Live data from Hacker News

/dev/null is an ACID compliant database

jyu.dev

11–20 of 203 posts

Re: /dev/null is an ACID compliant database

#15

Earlier quoted context omitted.

Yes, /dev/null can even power sites like zombo.com

What’s the I/O throughput of /dev/null ?

Single client, I'm getting ~5GB/s, both on an 8-year-old intel server, and on my M1 ARM chip.

However with a single server, it doesn't perfectly linearly scale with multiple clients. I'm getting

1 client: 5GB/s

2 clients: 8GB/s

3 client: 8.7GB/s

Re: /dev/null is an ACID compliant database

#16

Always instantly consistent, always available, and perfectly tolerant of partitioning. Truly, it is the only database which can be scaled to unlimited nodes and remain fully CAP.

Always available? Clearly you have not experienced situations with no /dev mounted.

Re: /dev/null is an ACID compliant database

#17

Earlier quoted context omitted.

Yes, /dev/null can even power sites like zombo.com

What’s the I/O throughput of /dev/null ?

You start dealing with Heisen-throughput at that point, it goes as high as you can measure.

Re: /dev/null is an ACID compliant database

#18
post #6

Always instantly consistent, always available, and perfectly tolerant of partitioning. Truly, it is the only database which can be scaled to unlimited nodes and remain fully CAP.

I guess we have a perfect idea for vaporware here. (pun intended) I am putting my marketing hat on right now.

Reminds me of Falso.

https://inutile.club/estatis/falso/

Re: /dev/null is an ACID compliant database

#19
post #16

Always instantly consistent, always available, and perfectly tolerant of partitioning. Truly, it is the only database which can be scaled to unlimited nodes and remain fully CAP.

Always available? Clearly you have not experienced situations with no /dev mounted.

One easy way to create such a situation is to use bwrap without --dev.

Re: /dev/null is an ACID compliant database

#20

Earlier quoted context omitted.

What’s the I/O throughput of /dev/null ?

Single client, I'm getting ~5GB/s, both on an 8-year-old intel server, and on my M1 ARM chip. However with a single server, it doesn't perfectly linearly scale with multiple clients. I'm getting 1 client: 5GB/s 2 clients: 8GB/s 3 client: 8.7GB/s

I'm easily reaching 30GB/s with a single client:

    dd if=/dev/zero of=/dev/null bs=1M status=progress
A second dd process hits the same speed.
Post reply on HN