n_u

6 ms·

31.
by n_u 9mo ago
what company?
32.
by n_u 9mo ago
> There is confusion about the less obvious benefits, confusion about how it works, confusion about the dangers (how do I adjust my well honed IPv4 spidey senses?), and confusion about how I transition my current private network Could yo
33.
by n_u 10mo ago
> I think they do need to ensure that page doesn't get flushed before the log entry in some manner. Yes I agree. I meant like they synchronously write the log entries, then return success to the caller, and then deal with dirty data
34.
by n_u 10mo ago
> I think there are a lot of reasons to use this flag besides a write()+f(data)sync() sequence: > * If you're putting something in a write-ahead log then applying it to the primary storage, you want it to be fully committed to th
35.
by n_u 10mo ago
Yeah that seems reasonable. The article seems to mix fsync and O_DSYNC without discussing their relationship which seems more like AI and less like a human who understands it. It also seems if you were using io_uring and used O_DSYNC you wo
36.
by n_u 10mo ago
I guess I'm a bit confused why the author recommends using this flag and fsync. Related: I would think that grouping your writes and then fsyncing rather than fsyncing every time would be more efficient but it looks like a previous c
37.
by n_u 10mo ago
> Submit the write to the primary file > Link fsync to that write (IOSQE_IO_LINK) > The fsync's completion queue entry only arrives after the write completes > Repeat for secondary file Wait, so the OS can re-order the fsy
38.
by n_u 10mo ago
Cool! I've always wanted something like this. Usually I just have to manually remove redundant CSS and styling options. Can you explain why the viewport width and height are needed?
39.
by n_u 11mo ago
Wireless ethernet adapters
40.
by n_u 11mo ago
What was the CRDT bug?
41.
by n_u 11mo ago
This was also my experience. TensorFlow's model of constructing then evaluating a computation graph felt at odds with Python's principles. It made it extremely difficult to debug because you couldn't print tensors easily! I
42.
by n_u 11mo ago
> PyTorch has dominated the AI scene since TF1 fumbled the ball at 10th yard line can you explain why you think TensorFlow fumbled?
43.
by n_u 1y ago
> Reranking: the highest value 5 lines of code you'll add. The chunk ranking shifted a lot. More than you'd expect. Reranking can many times make up for a bad setup if you pass in enough chunks. We found the ideal reranker set-
44.
by n_u 1y ago
Respecting robots.txt is a convention not enforced by anything so yes the bot is certainly free to ignore it. But I’m not sure I understand your distinction. A scraper is a crawler regardless of whether it is “custom”or an off the shelf sol
45.
by n_u 1y ago
Dumb question but just cuz I didn’t see it mentioned have you tried using a Disallow: / in your robots.txt? Or Crawl-delay: 10? That would be the first thing I would try. Sometimes these crawlers are just poorly written not malicious.
46.
by n_u 1y ago
Could you explain this some more? How are your costs so low in comparison? Are you using serverless?
47.
by n_u 1y ago
There was a recent VLDB paper[1] demonstrating that the extension DuckPGQ[2] for DuckDB (an embedded database) offers competitive graph query performance compared to Neo4j and Umbra. No data on how it compares to KuzuDB. [1] https:/&#
48.
by n_u 1y ago
> No foreign-keys allowed So it was sharded? And no cross-shard queries or txns were allowed? Or it was replicated? And no FKs were allowed because of consistency problems?
49.
by n_u 1y ago
Cool project! How do you generate the timestamps for last writer wins? What happens if there is a tie? Just my 2c: if I see a distributed database, the first question I ask is how it handles distributed transactions. Perhaps this topic shou
50.
by n_u 1y ago
Well bi-word matching requires that you still have all of the documents stored to verify the full phrase occurs in the document rather than just the bi-words. So it isn't always better. For example the phrase query "United States
51.
by n_u 1y ago
Cool project! I see you are using a positional index rather than doing bi-word matching to support positional queries. Positional indexes can be a lot larger than non-positional. What is the ratio of the size of all documents to the size of
52.
by n_u 1y ago
What are you building a vector database from scratch for?
53.
by n_u 1y ago
I'm more confused now. Those two have different logic? In the second example the balance can go negative. Also aren't both of those are going to have to lock the row to modify it? Even if you don't explicitly take out a lock
54.
by n_u 1y ago
> comparisons using clear sub-optimal interactive SQL transactions for financial workloads, like locking rows rather than using condition checks at commit time Could you give an example of how the same transaction could be written poorly
55.
by n_u 1y ago
Haha that's probably correct, databases are a huge topic and I still know very little. I learned most of what I know about databases from you and my work in industry. Perhaps could you share some of those good / bad things InnoDB
56.
by n_u 1y ago
P(two failures within MTTR for first node) = P(one failure)P(second failure within MTTR of first node|one failure) independence simplifies things = P(one failure)P(second failure within MTTR of first node) = P(one failure) * (1 - e^-λx) whe
57.
by n_u 1y ago
Ah yeah that makes sense. I guess if you are only using replica for fault tolerance and not as a read-replica then it seems semi-synchronous replication is strictly better than synchronous replication. I suppose in semi-sync the failover wi
58.
by n_u 1y ago
Thanks! I see. It's maybe a term they came up with to place it between async and fully synchronous replication.
59.
by n_u 1y ago
> write only needing to be written to the binary log on the replica and not (necessarily) applied to InnoDB. Ah. I wonder are writes in the log but not yet in InnoDB are available for reads? Then your write may succeed but a subsequent r
60.
by n_u 1y ago
> This made me laugh pretty hard, but it's basically my take too. Haha glad you enjoyed it. > It's interesting to me, though, that people see Postgres as the "big database" and MySQL as the "hobby database.&qu

More ›