n_u

7 ms·

61.
by n_u 1y ago
Hi, thank you for your work on this and being willing to answer questions on it. "We guarantee durability via replication". I've starting noticing this pattern more where distributed systems provide durability by replicating
62.
by n_u 1y ago
A couple dumb questions: 1. You say "ephemeral", but my understanding is that NVMe is non-volatile so upon crash and restart we should be able to recover the state of the memory. Is is ephemeral because of how EC2 works where you
63.
by n_u 1y ago
From my position MySQL pros: The MySQL docs on how the default storage engine InnoDB locks rows to support transaction isolation levels is fantastic. [1] This can help you better architect your system to avoid lock contention or understand
64.
by n_u 1y ago
Regarding cross-shard consistency, there's a doc here[1] on the options. In short you can just send the writes to all replicas, you can disallow cross-replica transactions (read and write), use two-phase commit to perform a distributed
65.
by n_u 1y ago
Thank you. From the doc > Automerge uses a combination of LWW (last writer wins) and multi-value register. By default, if you read from doc.foo you will get the LWW semantics, but you can also see the conflicts by calling Automerge.getCo
66.
by n_u 1y ago
Is there info anywhere on the structure of the semi-lattice they are using for their CRDT? Is the map based on a multi-value register or a last-writer-wins register?
67.
by n_u 1y ago
I agree with both of you. I think it’s sort of a hybrid and a spectrum of how much you do of each first. When you test part of the circuit with the scope, you are using prior knowledge to determine which tool to use and where to test. You d
68.
by n_u 1y ago
Ah I see. I thought by query you meant "user search query". I'm guessing by query here you mean "read".
69.
by n_u 1y ago
>It isn't the target of very many queries (relatively speaking) Wow why is that? Do you use a vector index primarily?
70.
by n_u 1y ago
Ah interesting. Is your keyword-document map (aka term dict) too big to keep in memory permanently? My understanding is that at Google they just keep it in memory on every replica. Edit: I should specify they shard the corpus by document so
71.
by n_u 1y ago
Which part of the index are you putting in the buffer pool here? The postings list, the doc store or the terms dict? Is it being cached for future queries or are you just talking about putting it in memory to perform the computation for a q
72.
by n_u 1y ago
It’s more about whether or not the company has taxable profits for that year (importantly these are not the same as real profits). I would read this article to understand more about how being forced to amortize tax deductions for expenses a
73.
by n_u 1y ago
It also classifies software development as R&D which together with immediate expensing for R&D undoes the Section 174 changes as far as I understand. “For purposes of this section, any amount paid or incurred in connection with the
74.
Changes to software dev tax Section 174 reverted(bloomberg.com)
4 points by n_u 1y ago|1 comments
75.
by n_u 1y ago
Relevant quote from article “Three business tax deductions would be made permanent. That includes the ability to use depreciation and amortization as the basis for interest expensing, the research and development write-off” from the bill it
76.
by n_u 1y ago
Signed and called my representative and senators. I ask simply "If I have $1m of revenue and $1m of expenses that is entirely software dev salaries, what do you think my profit is for that year? How much should I be taxed on that?&quot
77.
by n_u 1y ago
Some OTs do, some don't. OTs with the TP2 property do not require a central authority to order edits I believe. In my experience if you are persisting your edits or document state, you have something that creates an ordering anyways. T
78.
by n_u 1y ago
What I’ve always been curious about is if you can help the S3 query optimizer* in any way to use specialized optimizations. For example if you indicate the data is immutable[1] does the lack of a write path allow further optimization under
79.
by n_u 1y ago
It’s not addressed directly but I do think the article implies you hope your request latencies are not correlated. It provides a strategy for helping to achieve that > Try different endpoints. Depending on your setup, you may be able to
80.
by n_u 1y ago
I found a broadcast[1] of it and it seems the humans and robots run in separate lanes. It also looks like there are humans walking/running with the robots to hold them up if they start to fall over. Some of them need it and some of the
81.
by n_u 1y ago
Thanks for the example! I'll play around with it. > On my machine, the inflection point is around 10^14 goroutines - after which the mutex version becomes drastically slower; How often are you reaching 10^14 goroutines accessing a s
82.
by n_u 1y ago
Do you have any benchmarks for the pattern you described where channels are more efficient? > sync.Mutex, if left to wait long enough will enter a slow code path and if memory serves, will call out to a kernel futex. The channel will not
83.
by n_u 2y ago
Strong yes for 3 reasons 1. Reducing dev friction. When I had managers who coded they were ruthless about removing friction in the dev and deployment pipeline because they had to deal with it too. If build times went up, deployment infrastr
84.
by n_u 2y ago
> It is a curly-brace language What does this mean? Not Python?
85.
by n_u 2y ago
1. > However, customers still get a lot of value out keeping downstream systems synced with their warehouse tables. For instance, you can define which people you want to receive different campaigns and make sure that's consistent ac
86.
by n_u 2y ago
Did you test the "stop the world" approach? I wonder how the write downtime compares. It seems the 1 second of replication lag is unavoidable. The arbitrary 2.5 seconds of waiting for txns to finish could be removed by just killin
87.
by n_u 2y ago
Looks like you are also hiring a distributed systems engineer https://news.ycombinator.com/item?id=42920292 From that listing "Sync Speed: Customers want to sync a lot of data to important destinations like Facebook a
88.
by n_u 2y ago
> If we went with the ‘stop the world approach’, we’d have about the same kind of downtime as blue-green deployments: a minute or so. > After about a 3.5 second pause [13], the failover function completed smoothly! We had a new Postgr
89.
by n_u 2y ago
They say the "stop the world" approach that causes more downtime is Turn off all writes. Wait for 16 to catch up Enable writes again — this time they all go to 16 and instead they used a better algorithm: Pause all
90.
by n_u 2y ago
To add onto this I feel like one of the hard things about TF is that there is like at least 3 ways to do everything because they have supported multiple APIs and migrated to eager. So if you find an example or an open source project it migh

More ›