31–40 of 203 posts
Considering there is no way to read back data written to /dev/null it will not be useful for storing database data.
Best stack cloud providers don't want you to know about, /dev/null for db and https://github.com/kelseyhightower/nocode for the backend.
/dev/null is not a database. By this logic is a hard disk a database, is a CD a database. No. They are storage mediums. You could store a database on them, but they themselves are not a database. Considering there is no way to read back data written to /dev/null it will not be useful for storing database data.
But is /dev/null web scale?
Best stack cloud providers don't want you to know about, /dev/null for db and https://github.com/kelseyhightower/nocode for the backend.
WTF is going on with the issues and pull requests for that repo?
Best stack cloud providers don't want you to know about, /dev/null for db and https://github.com/kelseyhightower/nocode for the backend.
WTF is going on with the issues and pull requests for that repo?
Earlier quoted context omitted.
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.
My artisanal architecture design uses writes with a few characters and uses unix pipes: yes | pv > /dev/null I hope that in my next rewrite I can advance to larger block sizes.
yes $(printf %1024s | tr " " "y") | pv > /dev/null