3 ms·
It's stated that the goal is to fit file icons into inodes to avoid additional disk accesses. How much of an issue is this on an SSD instead of a hard disk?
by rcthompson 10y ago
It's stated that the goal is to fit file icons into inodes to avoid additional disk accesses. How much of an issue is this on an SSD instead of a hard disk?
- captainmuon 10y agoAlso, doesn't every modern OS use an icon cache? So you'd only read the icon once for every file type.
- wongarsu 10y agoIt's much less of an issue than with HDDs, but random read latency to a fast SSD is still in the order of magnitude of 100,000 clock cycles or slower.
- ldjb 10y agoI'm curious as to how you'd update the icon for a file type. Would you have to update the inode of every single file of that type? That can't be too efficient. I'm sure there are ways of getting around the problem, but having lots of duplicate data (even if each icon is very small) isn't generally a good idea (but perhaps this is an exception).
- rcthompson 10y agoYeah, I'm a bit confused about what this is for. Any icons common to an entire file type should be cached in RAM already, so I the only thing I can think of would be file-specific icons. But I expect most of those would be thumbnail images, which would not be amenable to a concise vector representation.