Linked by Thom Holwerda on Sun 14th Apr 2013 20:30 UTC
Hardware, Embedded Systems "In the past five years, flash memory has progressed from a promising accelerator, whose place in the data center was still uncertain, to an established enterprise component for storing performance-critical data. It's rise to prominence followed its proliferation in the consumer world and the volume economics that followed. With SSDs, flash arrived in a form optimized for compatibility - just replace a hard drive with an SSD for radically better performance. But the properties of the NAND flash memory used by SSDs differ significantly from those of the magnetic media in the hard drives they often displace. While SSDs have become more pervasive in a variety of uses, the industry has only just started to design storage systems that embrace the nuances of flash memory. As it escapes the confines of compatibility, significant improvements in performance, reliability, and cost are possible."
Permalink for comment 558593
To read all comments associated with this story, please click here.
RE[3]: Comment by TempleOS
by ssokolow on Tue 16th Apr 2013 00:33 UTC in reply to "RE[2]: Comment by TempleOS"
Member since:

The Linux devs are playing around with compressing allocated memory to increase transfer times and use RAM more efficiently.

True, but from what I understand, that's more like swap space and it can't achieve the same compression ratios as data-aware formats like PNG. (Remember, PNG performs various transforms before DEFLATEing)

With ECC RAM, RAM already has checksums, and checksummed RAM pages, at the OS level, would increase security.

Point. I keep forgetting how much acceleration for checksum-related stuff is available in modern CPU instruction sets.

OS X already renders everything in PDF, and it pre-renders icons and things of different sizes then stores them in an on-disk cache.

Point. I suppose it could work as long as there's a strong effort to shame and shun any applications which put their caches somewhere that can't be expired independent of their cooperation or knowledge.

Every conceivable version doesn't have to be pre-rendered. Only the most common sizes need to be pre-rendered, or only the rendered sizes need to be cached. Plus, the rendered versions don't have to be saved with the original file.

I was under the impression "the most common size" for a PDF was "Fit Width".

Also, I'm Canadian. I've got 5Mbit/800Kbit Internet and every member of my family (my writer/artist mother, my gamer brothers, my non-gaming, programming self, etc.) can never have enough disk space so wasting space on easily-regenerated caches for rarely-used files is not acceptable from a storage OR a transfer perspective.

"Pre-rendering the most common sizes" is only acceptable for things like icon themes where you can typically count the number installed on one hand and even the biggest ones have a small "per page" size.

Reply Parent Score: 3