Timeline for Can I configure my Linux system for more aggressive file system caching?
Current License: CC BY-SA 4.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Sep 5, 2024 at 8:54 | comment | added | mjaggard | @Cobra_Fast OP already stated that all their data fits in RAM so why not readahead the whole file for every file you read? Seems like a good option to me. | |
| S Aug 21, 2021 at 9:07 | history | suggested | france1 | CC BY-SA 4.0 |
improoved and commented
|
| Aug 21, 2021 at 8:09 | review | Suggested edits | |||
| S Aug 21, 2021 at 9:07 | |||||
| Jun 15, 2015 at 22:32 | comment | added | Cobra_Fast | @syss the readahead settings are saved as number of memory "blocks", not bytes or bits. The size of one block is determined at kernel compilation time (since readahead-blocks are memory blocks) or filesystem creation time in some cases. Normally though, 1 block contains 512 or 4096 bytes. See linux.die.net/man/8/blockdev | |
| Jun 15, 2015 at 19:22 | comment | added | syss | @Cobra_Fast Do you know what it means? I really have no idea and I am interested now. | |
| Dec 25, 2013 at 4:11 | comment | added | Cobra_Fast | 3GB or 2TB readahead? really? Do you even know what these options do? | |
| Mar 14, 2012 at 21:03 | history | answered | Ole Tange | CC BY-SA 3.0 |