The release notes for the final production release of the Optane Memory and RST drivers even includes in the list of fixed issues the removal of the ability to enable Optane caching with a non-Optane NVMe cache device, and the ability to turn on Optane caching with a Skylake processor in a 200-series motherboard. The only genuine hardware requirement seems to be a Skylake 100-series or later chipset. Many of these restrictions are arbitrary and software enforced. Motherboards that have the necessary firmware features will feature a UEFI tool to unpair the Optane Memory cache device from the backing device being cached, but this can also be performed with the Windows software. Lastly, the motherboard firmware must have Optane Memory support to boot the cached volume. The drive being cached must be SATA, not NVMe, and only the boot volume can be cached. The Optane Memory module must be installed in a M.2 slot that connects to PCIe lanes provided by the chipset, and some motherboards will also have M.2 slots that do not support Optane Caching or RST RAID. Windows 10 64-bit is the only supported operating system. Only Core i3, i5 and i7 processors are supported Celeron and Pentium parts are excluded. Optane Memory caching has quite a few restrictions: it is only supported with Kaby Lake processors and it requires a 200-series chipset or a HM175, QM175 or CM238 mobile chipset. The Optane Memory software can be downloaded and installed separately without including the rest of the RST features. It relies on the same NVMe remapping feature added to Skylake chipsets to support NVMe RAID, but the caching algorithms are tuned for Optane. Intel's caching solution for Optane Memory is not simply a re-use of the existing Smart Response Technology caching feature of their Rapid Storage Technology drivers. The rapidly dropping prices and increasing capacities of SSDs made all-flash configurations more and more affordable, while SSD caching still required extra work to set up and small cache sizes meant heavy users would still frequently experience uncached application launches and file loads. Smart Response Technology worked as advertised but was very unpopular with OEMs, and it didn't really catch on as an aftermarket upgrade among enthusiasts. These SSDs started at $100 and had to compete against MLC SSDs that offered multiple times the capacity for the same price-enough that the MLC SSDs were starting to become reasonable options for every general-purpose storage without any hard drive. Intel produced the SSD 311 and later SSD 313 with low capacity but relatively high performance SLC NAND flash as caching-optimized SSDs. SRT could be used with any SATA SSD but cache sizes were limited to 64GB. The Z68 chipset for Sandy Bridge processors added Smart Response Technology (SRT), a SSD caching mode for Intel's Rapid Storage Technology (RST) drivers. Intel's next attempt at caching came as SSDs were moving into the mainstream consumer market. Overall, most OEMs were not interested in adding more than $100 to a system for Turbo Memory. Battery life could sometimes be extended by allowing the hard drive to spend more time spun down in idle. Applications were seldom significantly faster, though in systems short on RAM, Turbo Memory made swapping less painfully slow. The cache it provided was far too small and too slow-sequential writes in particular were much slower than a hard drive. Promoted as part of the Intel Centrino platform, Turbo Memory was more or less a complete failure. In a day, IAStorDataSvc has gone from 30MB to 600MB and iasm from 20MB to 250MB.Intel's first attempt at using solid-state memory for caching in consumer systems was the Intel Turbo Memory, a mini-PCIe card with 1GB of flash to be used by the then-new Windows Vista features Ready Drive and Ready Boost. If not, is there a way to cap the amount of memory these processes are using, without crashing Win 10?.There are also a few svhost processes displaying high usage but I couldn't trace them. I get my information from Windows' Task Manager and Task Monitor, which somehow do not seem to show every process (the total of all the processes displayed does not amount to the Total Memory Used as shown in the Summary Graph there are a few GB missing). This has resulted in a crash already, and now I have to reboot the computer every week to avoid it. Last time I've checked, IAStorDataSvc would actually plateau after ~5 days (I don't know how long for), but iasm keeps crawling up. They would start at around 30MB after a reboot and end up above 2GB after a week. The main culprit I could found were IAStorDataSvc and iasm. Since this computer is started with only one program running, and none other after this, it feels like there is a memory leak. I've noticed on one of our computers that some Intel RST processes are using a lot of memory, and more worryingly, that the usage is increasing with time.
0 Comments
Leave a Reply. |