4 ms·
I thought Linux buffering holds everything important in RAM anyway, no? If I had 1GiB of files served by Apache/Nginx and changed only once every 24 hours, then
by atmanactive 1y ago
I thought Linux buffering holds everything important in RAM anyway, no? If I had 1GiB of files served by Apache/Nginx and changed only once every 24 hours, then, stuffing it all in a RAM disk wouldn't make any difference on performance. Or would it?
- compressedgas 1y agoYes, but there is no means to pin files and directories into memory so that they never get evicted from the file system cache. If there were, one could use that instead.
- atmanactive 1y agoAs long as they are used, they are there.
- mokulanis 1y agoNo i would not. I am using a RAM disk for compiling large projects, especially with a size of several terabytes, is a brilliant solution for your company. It totally makes sense given how compilation cycles can just chew through SSDs while HDDs are too slow.
- atmanactive 1y agoThat's a valid use case, thank you. Writing being the key here.
- nolist_policy 1y agoI have found that temporary files are flushed much less by btrfs than ext4. ext4 will do a disk write io for every created file, even if it's only a temporary file. For btrfs, new files that are deleted before write back will never hit the disk.