I'm under the impression that, because of the hard limit on writes, OSes often already cache writes to SSDs, further limiting their usefulness in this kind of application.
On Friday, March 6, 2015 at 4:10:54 PM UTC-5, Fluid Dynamics wrote: > > On Friday, March 6, 2015 at 3:16:09 PM UTC-5, Michael Blume wrote: >> >> Possibly stupid question: can you just pretend you have more memory than >> you do and let the operating system do the heavy lifting? >> > As in, put the swap partition on the SSD and jack up the virtual memory in > the OS config? > > Isn't it a bad idea to put swap on an SSD, because of the limited number > of times an SSD byte can be rewritten before it sticks permanently? Thus > making SSD more suited to storing stuff where speed counts, but which > doesn't change very much, like the operating system kernel and modules and > core libraries, plus your most often used applications? Then you get faster > boot and app-startup times without constant writes to the SSD (just when > something is upgraded). > > Of course, SSD being less well suited to frequently-written data would > also militate against using it for a cache managed by the application, > rather than by the OS ... > > -- You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to clojure@googlegroups.com Note that posts from new members are moderated - please be patient with your first post. To unsubscribe from this group, send email to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en --- You received this message because you are subscribed to the Google Groups "Clojure" group. To unsubscribe from this group and stop receiving emails from it, send an email to clojure+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
