O_HOT and O_COLD
Posted Apr 28, 2012 19:51 UTC (Sat) by giraffedata
Parent article: O_HOT and O_COLD
Given that differences exist, it is natural to want to place more frequently-accessed data on the faster part of the device.
The proposal seems to do something rather diffferent: rather than steer data to a faster part of the device, it creates a faster part of the device. It's faster because the head happens to be positioned there most of the time.
Also, it doesn't seem to account for an important reality of temperature: your hottest data should go on the slowest device, because it's accessed on the device rarely (it's accessed in an intervening cache most of the time).
to post comments)