Razer Leviathan V2 gaming soundbar review
Guru3D NVMe Thermal Test - the heatsink vs. performance
EnGenius ECW220S 2x2 Cloud Access Point review
Alphacool Eisbaer Aurora HPE 360 LCS cooler review
Noctua NH-D12L CPU Cooler Review
Silicon Power XPOWER XS70 1TB NVMe SSD Review
Hyte Y60 chassis review
ASUS ROG Thor 1000W Platinum II (1000W PSU) review
ASUS ROG Rapture GT-AXE11000 WIFI6E router review
Backforce One Plus Gaming Chair review
Crucial launches nvdimm memory
Crucial (Micron) today launches nvdimm memory for server. It is quite interesting as this type of memory combines dram and nand on one single module. This way you will get the performance of dram but during a power outage, your data will remain intact.
Nvdimm is short for nonvolatile DIMM memory and takes a seat into DDR4 memory slots of servers. The 288pin DIMMs offer a speed of 2133MT/s and a bandwidth of 17 GB/s . The memory operates at the standard JEDEC voltage of 1.2V . When a power outage or other interruption system controller transmits the signal to the module so that the data of the dram to the non - volatile memory will be written.
Once power kicks back in allows the controller will write the data to dram again, at that point the system can continue as-is. Crucial sells nvdimm as a separate module and a 2.5 " -formfactor combined with a PowerGem capacitor from AgigA Tech, which temporarily keeps the DIMM powered during outages. Crucial only offers 8GB nvdimms. According to Micron 16GB versions are coming.
Crucial MX300 SSDs with 3d-nand - 05/19/2016 06:45 PM
Micron has released the new Crucial MX300 SSD series that will make use of 3D Nand (vertical stacked NAND), it is TLC written. The product will become available in 275GB up-to 2 TB volume sizes. A 750...
Crucial Announces Ballistix Sport LT DDR4 SODIMMs - 05/17/2016 05:31 PM
New modules give gamers more speed, more performance, and better gaming. Crucial, a leading global brand of memory and storage upgrades, today announced the availability of Ballistix Sport LT DDR4 SO...
Micron to release Crucial MX300 SSDs with 3d-nand this summer - 05/04/2016 08:23 AM
Micron will be releasing a Crucial MX300 SSD series that will make use of 3D Nand (vertical stacked NAND), it is TLC written. The product will become available in 275GB up-to 2 TB volume sizes. A 7...
Crucial DDR4 2400MT/s 8Gb-based Server Memory Available - 12/09/2015 10:09 AM
Crucial announced the availability of Crucial DDR4 2400MT/s 8Gb-based RDIMM, LRDIMM and ECC UDIMM server modules. Engineered to enable higher density modules, 8Gb-based DDR4 enables increased performa...
Crucial Launches Budget BX200 SSD - 11/03/2015 04:19 PM
Crucial announced their Crucial BX200 solid state drive (SSD), which offers affordable performance. The drive, designed for consumers and SMBs, allows users to load applications in seconds, boot up al...
WareTernal
Senior Member
Posts: 256
Joined: 2013-09-27
Senior Member
Posts: 256
Joined: 2013-09-27
#5293166 Posted on: 06/21/2016 06:50 PM
I'm reading that it only writes to NAND when the power is interrupted.
I'm still not sure how this would work. Are they saying we wouldn't need to reboot the server? It would just magically skip the 5-10 minute boot process and just jump right back to its previous running state? I can't see that happening....
Memory, that's a lot of changed bits every second on server. If it is stored on nand...
I'm reading that it only writes to NAND when the power is interrupted.
I'm still not sure how this would work. Are they saying we wouldn't need to reboot the server? It would just magically skip the 5-10 minute boot process and just jump right back to its previous running state? I can't see that happening....
Fox2232
Senior Member
Posts: 11809
Joined: 2012-07-20
Senior Member
Posts: 11809
Joined: 2012-07-20
#5293180 Posted on: 06/21/2016 07:11 PM
I'm reading that it only writes to NAND when the power is interrupted.
I'm still not sure how this would work. Are they saying we wouldn't need to reboot the server? It would just magically skip the 5-10 minute boot process and just jump right back to its previous running state? I can't see that happening....
Then They have to have capacitors or backup battery which will keep memory operational during writing data to nand.
That would work. Data in CPU cache would still be lost, unless even CPU/MB has UPS backup. And as it reaches low power it would trigger 'suspend to ram'.
With 'suspend to ram' CPU no longer works on data and as UPS runs out of power, memory will write its nand.
Upon recovery of electricity delivery system has to initiate reverse 'suspend to ram'.
How that's triggered when entire MB goes out of power, I do not know.
But considering all complications in this chain and requirements to have UPS anyway to prevent errors from CPU cache loss...
I think UPS + classical software initiated hibernation is practically same solution with less complications.
Hell, Even my UPS can tell to PC to shutdown/hibernate when it is running out of juice.
I'm reading that it only writes to NAND when the power is interrupted.
I'm still not sure how this would work. Are they saying we wouldn't need to reboot the server? It would just magically skip the 5-10 minute boot process and just jump right back to its previous running state? I can't see that happening....
Then They have to have capacitors or backup battery which will keep memory operational during writing data to nand.
That would work. Data in CPU cache would still be lost, unless even CPU/MB has UPS backup. And as it reaches low power it would trigger 'suspend to ram'.
With 'suspend to ram' CPU no longer works on data and as UPS runs out of power, memory will write its nand.
Upon recovery of electricity delivery system has to initiate reverse 'suspend to ram'.
How that's triggered when entire MB goes out of power, I do not know.
But considering all complications in this chain and requirements to have UPS anyway to prevent errors from CPU cache loss...
I think UPS + classical software initiated hibernation is practically same solution with less complications.
Hell, Even my UPS can tell to PC to shutdown/hibernate when it is running out of juice.
MM10X
Senior Member
Posts: 4240
Joined: 2008-08-21
Senior Member
Posts: 4240
Joined: 2008-08-21
#5293215 Posted on: 06/21/2016 08:29 PM
I don't really see the practicality of this application...
Most data centers, like the one I'm sitting in, have redundant generators. If the city grid loses power the building can still stay running without interruption for several days.
I don't really see the practicality of this application...
Most data centers, like the one I'm sitting in, have redundant generators. If the city grid loses power the building can still stay running without interruption for several days.
schmidtbag
Senior Member
Posts: 6551
Joined: 2012-11-10
Senior Member
Posts: 6551
Joined: 2012-11-10
#5293246 Posted on: 06/21/2016 09:54 PM
Memory, that's a lot of changed bits every second on server. If it is stored on nand...
What's life expectancy? Do they use like 64GB nand on 8GB memory module to actually keep it from sudden death?
I was thinking the same thing... I can't imagine this lasting much longer than a year or two in the average server. Not to mention, there will hardly be any hardware out there that can actually take advantage of the non-volatile feature.
As stated by others, it's better to just use backup power sources and redundancy. Even if it's just a brownout, a few seconds of downtime could cost a fortune for companies that could afford something like this (especially if it has a very limited lifespan, and requires frequent replacement).
Is this even ECC or buffered?
EDIT:
Just an afterthought - seeing as most servers run Linux, it's possible to "freeze" applications. Meaning, you can effectively hibernate the program without closing it or shutting off the computer, where you can then restore the application later on. If retaining a memory status is really so important, to me, it'd make more sense to use a cron job to freeze the application every 10 minutes or so. Depending on what's being processed, 10 minutes of lost time is better than several hours. Still a stupid idea, regardless.
Memory, that's a lot of changed bits every second on server. If it is stored on nand...
What's life expectancy? Do they use like 64GB nand on 8GB memory module to actually keep it from sudden death?
I was thinking the same thing... I can't imagine this lasting much longer than a year or two in the average server. Not to mention, there will hardly be any hardware out there that can actually take advantage of the non-volatile feature.
As stated by others, it's better to just use backup power sources and redundancy. Even if it's just a brownout, a few seconds of downtime could cost a fortune for companies that could afford something like this (especially if it has a very limited lifespan, and requires frequent replacement).
Is this even ECC or buffered?
EDIT:
Just an afterthought - seeing as most servers run Linux, it's possible to "freeze" applications. Meaning, you can effectively hibernate the program without closing it or shutting off the computer, where you can then restore the application later on. If retaining a memory status is really so important, to me, it'd make more sense to use a cron job to freeze the application every 10 minutes or so. Depending on what's being processed, 10 minutes of lost time is better than several hours. Still a stupid idea, regardless.
Click here to post a comment for this news story on the message forum.
Senior Member
Posts: 11809
Joined: 2012-07-20
Memory, that's a lot of changed bits every second on server. If it is stored on nand...
What's life expectancy? Do they use like 64GB nand on 8GB memory module to actually keep it from sudden death?