|
|
Archaic methodology
I've never understood why ram disks still exist. Caching completely replaces the need for ram disks in the read-only world, i.e. everyone knows that you should never put an application in a ram disk. Likewize, improving caching technology to handle the complexities of the read-write world would seem to be the intelegent place to direct your efforts. For example, programs like ProjectBuilder could label all their intermediate build files as "unimortent / never save to disk" and label all the basic source files as "critical / cache in emergency crash resistant ram or flash." You could also have a "high preformance file" checkbox in the file info editor, but this is probably a waist of the users time. Anyway once the OS know what the use really cared about, it could just happily go about not spinning up the harddrive for extended periods of time.
Useful in the real world
So what you're saying is, we should redesign the OS's cache management and filesystem semantics and rewrite all applications, to avoid what you feel is an improper technique (using a ramdisk). O-kay. |
SearchFrom our Sponsor...Latest Mountain Lion HintsWhat's New:HintsNo new hintsComments last 2 daysLinks last 2 weeksNo recent new linksWhat's New in the Forums?
Hints by TopicNews from Macworld
From Our Sponsors |
|
Copyright © 2014 IDG Consumer & SMB (Privacy Policy) Contact Us All trademarks and copyrights on this page are owned by their respective owners. |
Visit other IDG sites: |
|
|
|
Created this page in 0.21 seconds |
|