3 ms·
> doesn't seem too important or interesting in my day to day app and distributed systems development. Makes sense to me. At Google we were told to stop thinkin
by jeffbee 4y ago
> doesn't seem too important or interesting in my day to day app and distributed systems development.
Makes sense to me. At Google we were told to stop thinking about all this stuff, that the storage hardware and software people were responsible for hiding things like wearout from application developers. This article is really "things you should know if you plan to directly access an NVMe device" but there is a huge class of programmers who are better off not knowing.
- bombcar 4y agoThere was an article by varnish taking about how you should leave the caching and memory management to the OS - even if you can beat the virtual memory manager today you’ll stop improving your home grown solution while RAM and the kernel keep marching on.
- wmf 4y agohttps://varnish-cache.org/docs/trunk/phk/notes.html https://varnish-cache.org/docs/trunk/phk/notes.html
- rasz 4y ago>At Google we were told to stop thinking about all this and as a result Chrome slams SSD by writing cached Youtube videos to disk .... except Youtube never reuses cached video data (not even when rewinding more than couple minutes to already watched spot in same video), it explicitly generates hashed requests with custom URL parameters googlevideo.com/videoplayback?expire (~6hour shelf life) &range &sig &lsig. Heavy YT viewing results in wearing out your SSD by tens of gigabytes per day for no particular reason. This is just one small example of side effects from such brilliant decisions.
- MichaelZuo 4y agoYikes, is that really the case? No wonder the 128GB drive on my 2013 MacBook air wore out to 60% of its original performance...