gitgudnubs

7 ms·

31.
by gitgudnubs 7y ago
I didn't set the parameters of the question. I didn't consider investing the money either, proving that I was literally just responding to the scenario as presented. I chose San Fransisco, because it's close to home for poste
32.
by gitgudnubs 7y ago
Your calculations are based on an erroneous model. Corporate profits are taxed twice. The effective tax rate of dividends can be as high as 39.8%. I'm not sure what typical numbers are, because I couldn't find 2018 data, and 2017
33.
by gitgudnubs 7y ago
A single person in San Fransisco with an income of $500,000 and the standard deduction has a takes home $288,646. A single person in San Fransisco has a cost of living of $1125.83 without rent, according to numbeo (whatever that is). Median
34.
by gitgudnubs 7y ago
You're racist for thinking that the word "black" used to refer to something as bad is at all related to dark skinned people.
35.
by gitgudnubs 7y ago
You haven't eliminated them. You've just moved them into a dedicated co-processor. Co-processors are cheap when they're ubiquitous, like DMA. Co-processors are expensive when they're in custom hardware, like K-V stores.
36.
by gitgudnubs 7y ago
It's the same in both cases. You write a dirty mapping in memory. You persist the value, and you persist the mapping. Then you flip the dirty bit.
37.
by gitgudnubs 7y ago
Exactly. It's a beautiful concept: the server is roughly half the TCO per gigabyte. That can decrease significantly with better architectures, as shown by this. But making it 2x1GbE is a huge complicating factor. And 2.5GbE is way out
38.
by gitgudnubs 7y ago
If I were going to sell a network attached spinning disk at scale, then I would probably target 2.5GBASE-T. The problem there is that no routers support it.
39.
by gitgudnubs 7y ago
>it was a straight jump from 1GbE and it was relatively easy. It wasn't relatively easy, because you can't run 10GBASE-T over Cat5e, and because a 10GbE NIC was as expensive as the rest of the drive put together. Today you can
40.
by gitgudnubs 7y ago
Network attached HDDs were killed by ethernet. In their infinite wisdom, ethernet decided there was no need for speeds between 1GbE and 10GbE. They finally caved to reality with 40GbE, 25GbE, and 50GbE. They eventually ratified 2.5GbE, but
41.
by gitgudnubs 7y ago
No it doesn't. The SSD lookup is measured in microseconds. The memory lookup for the mapping to blkid is measured in nanoseconds. Unless they're putting some expensive, power-hungry CAM in these devices, they're doing exactly
42.
by gitgudnubs 7y ago
Ok.... I can just store the mapping of content key to blkid. Then I can load the mapping into memory. Then I have a key value store on an SSD using cheap, available hardware.