Slashdot Mirror


Intel Unveils Optane SSD DC P4800X Drive That Can Act As Cache Or Storage (hothardware.com)

MojoKid writes from a report via HotHardware: Intel unveiled its first SSD product that will leverage 3D Xpoint memory technology, the new Optane SSD DC P4800X. The Intel SSD DC P4800X resembles some of Intel's previous enterprise storage products, but this product is all new, from its controller to its 3D Xpoint storage media that was co-developed with Micron. The drive's sequential throughput isn't impressive versus other high-end, enterprise NVMe storage products, but the Intel Optane SSD DX P4800X shines at very low queue depths with high random 4kB IO throughput, where NAND flash-based storage products tend to falter. The drive's endurance is also exceptionally high, rated for 30 drive writes per day or 12.3 Petabytes Written. Intel provided some performance data comparing its SSD SC P3700 NAND drive to the Optane SSD DC P4800X in a few different scenarios. This test shows read IO latency with the drive under load, and not only is the P4800X's read IO latency significantly lower, but it is very consistent regardless of load. With a 70/30 mixed read write workload, the Optane SSD DC P4800X also offers between 5 and 8x better performance versus standard NVMe drives. The 375GB Intel Optane SSD DC P4800X add-in-card will be priced at $1520, which is roughly three times the cost per gigabyte of Intel's high-end SSD DC P3700. In the short term, expect Intel Optane solid state drives to command a premium. As availability ramps up, however, prices will likely come down.

63 comments

  1. XPoint by sexconker · · Score: 1

    Stay away from Xpoint (Optane) products for a while.
    They're far, far off their initial promises, which points to manufacturing issues.

    http://semiaccurate.com/2016/0...

    1. Re:XPoint by haruchai · · Score: 1

      Stay away from Xpoint (Optane) products for a while.
      They're far, far off their initial promises, which points to manufacturing issues.

      http://semiaccurate.com/2016/0...

      I imagine OCZ must have mixed feelings about any Optane story given their Octane SSDs debuted 5 years ago

      --
      Pain is merely failure leaving the body
  2. This post by Anonymous Coward · · Score: 0

    This post is a little late, but it's still pretty good.

    1. Re:This post by wonkey_monkey · · Score: 1

      I've seen better.

      --
      systemd is Roko's Basilisk.
    2. Re:This post by Anonymous Coward · · Score: 0

      It wasn't even a very subtle joke. I worry for Slashdot. Well I don't really.

  3. Just a bunch of blocks? by thogard · · Score: 1

    When are we going to get drives that are just a bunch of blocks so that we can do our own wear and use leveling? Why should I trust a tiny computer on the SSD when I've got one that can do far more on the other end of the SATA line?

    1. Re:Just a bunch of blocks? by EndlessNameless · · Score: 1

      Not soon, probably never.

      The disk controller interfaces deliberately abstract those writeable areas. You would need to toss SATA/NVMe entirely and develop a new standard.

      This leaves the SSD manufacturers free to choose a variety of controllers and flash chips, and they can optimize the firmware for their hardware without worrying about meddling from userspace.

      Even if you did develop a standard that obstensibly provides direct access to low-level sectors, there is nothing in the world that you can do to stop a manufacturer from implementing a renaming/remapping scheme in their firmware.

      So, basically, it is impossible to guarantee the kind of low-level access you want. Since everything seems to be working quite fine without it, I don't see why anyone would bother reinventing the wheel in the first place.

      --

      ---
      According to the latest ruleset, this post should be modded as Vorpal Flamebait +5.
    2. Re: Just a bunch of blocks? by Anonymous Coward · · Score: 0

      It should be open source! Who is spying on our clusters....

    3. Re:Just a bunch of blocks? by Trogre · · Score: 1

      What you're proposing is effectively ditching Integrated Drive Electronics and going back to CPU or card-based disk controllers.

      I look forward to seeing 1701 error codes again.

      --
      "Nine times out of ten, starting a fire is not the best way to solve the problem." - my wife
  4. Cache? by wonkey_monkey · · Score: 2

    Intel Unveils Optane SSD DC P4800X Drive That Can Act As Cache Or Storage

    I might be missing something, but if you're going to mention that it can act as cache it would be nice to include something about that bit in the summary.

    No-one reads TFA anyway, of course, but in this case it's counter-blocked because I'm using uBlock, so I'm doubly put off.

    --
    systemd is Roko's Basilisk.
    1. Re:Cache? by Sarusa · · Score: 2

      Yeah, because it's not true. It doesn't work well as cache, and if you tried it you'd burn it out fast. It was SUPPOSED to, they promised a lot that you could use this as both storage as main memory, but they couldn't make it work and even Intel has stopped talking about Apache Pass.

      Basically, this is a evolutionary step in flash, giving you much faster random write and maybe 2x the endurance for 2x the price, so not bad as a disk.

      But it's not the revolutionary step Intel was promising.

    2. Re:Cache? by Anonymous Coward · · Score: 0

      Get this anti-adblock killer script and never worry about uBlock counter-blocks anymore.

      https://github.com/reek/anti-adblock-killer

    3. Re:Cache? by TheRaven64 · · Score: 1

      The endurance listed is 30 drive writes per day for the 375GB model. That's 11.25TB/day, or about 130MB/s sustained 24/7 writes. A cache device should be spending 90% of its time being read, rather than written (or it's not doing that good a job as a cache[1]), which means that even if you're reading from it at about half of its peak rate every second of every day and getting then it's going to last its rated lifetime. Additionally, for a cache device, we really don't care if it burns out. When it does, we don't lose any data, we just take a performance hit until it can be replaced (we've had flash L2 ARC devices die quite a few times), but we really do care a lot about random read performance from the cache drive while it's working.

      [1] I just checked the ARC stats on one of our machines. We're getting over 98% hit rates from the ARC and only about 55% from the L2 ARC, so we'd probably wear out one of these a bit faster. That said, this machine has 256GB of RAM and is only using 320GB of L2 ARC, so it's not too surprising that the L2 ARC is not doing a great job: once the working set goes past about 150-200GB (ARC size), it's going to grow past 500GB (ARC + L2 ARC size) pretty quickly.

      --
      I am TheRaven on Soylent News
    4. Re: Cache? by Anonymous Coward · · Score: 0

      What the heck are you talking about? I'm currently at the Linux Filesystem Storage and MM conference and Intel reps brought Apache Pass DIMMs.

    5. Re:Cache? by Sarusa · · Score: 1

      It's not great for reads though - Even the consumer m.2 SSD in my PC is faster for that. It's just really fast on small random writes, or small reads under LOW read/write load (small queue depth) because it really wins for latency there. So you have to be using it on something with lots of writes and low load small reads to get amazing benefit over current flash - and then it burns out fast.

      I'm sure there will be some very targeted applications where this is perfect, like maybe mostly data acquisition and high speed db updates then at the end of the week you pop it out and put in a new one and you've got your snapshot and can go analyze the data on that.

    6. Re: Cache? by Sarusa · · Score: 1

      They're still looking at Apache Pass for 2018, but it's dead as a product /now/ for Skylake-EP/Purley and they're playing it down. At IDF 2015 it was 'Apache Pass Apache Pass Apache Pass' and at IDF 2016 it was 'Uh, yeah we'll have DIMMS', and now it's 'Wow, this is great for SSDs.'

      I'm not surprised they brought some DIMMs to show (it's not dead dead, just not now), but I'm genuinely curious about this: Ask when you can buy some.

    7. Re: Cache? by Panaflex · · Score: 1

      Honestly I could care less about another SSD technology - having good NVRAM on the memory bus is one of the most exciting things in system design I've seen in a long time.

      I may be wrong - but in my experience a minimum of 10% of runtime at load, and at least 25-30% of OS code is all about hiding the fact that storage speed sucks and we have to stuff everything through a storage protocol. New IO designs could open up some very cool technologies that currently depend on clunky NAND/flash limitations.

      --
      I said no... but I missed and it came out yes.
  5. Its rather exaggerated by m.dillon · · Score: 5, Interesting

    Intels claims are rather exaggerated. Their claims have already been torn apart on numerous tech forums. At best we're talking only a ~3-5x reduction in QD1 latency and the intentionally omit vital information in the specs to force everyone to guess what the actual durability of the XPoint devices is. They say '12PB' of durability for the 375GB part but refuse to tell us how much overprovisioning they do. They say '30 drive writes per day' without tellling us what the warrenty will be.

    In fact, over the last 6 months Intel has walked back their claims by orders of magnitude, to the point now where they don't even claim to be bandwidth competitive. They focus on low queue depths and and play fast and loose with the stats they supply.

    For example, their QOS guarantee is only 60uS 4KB (99.999%) random access latency and in the same breath they talk about being orders of magnitude faster than NAND NVMe devices. They fail to mention that, for example, the Samsung NVMe devices also typically run around ~60-70uS QD1 latencies. Then Intel mumbles about 10uS latencies but bandies about large factors of improvement over NAND NVMe devices, far larger than the 6:1 one gets simply assuming 10uS vs 60uS.

    Then they go on to say that they will have a NVDIMM form for the device later this year, with much faster access times (since in the NVMe form factor access times are constricted by the PCIe bus and block I/O protocol). But with potentially only 33,000 rewrite cycles per cell to failure that's seriously problematic. (And that's the best guess, since Intel won't actually tell us what the cell durability is).

    --

    The price point is way too high for what XPoint in the NVMe format appears to actually be capable of doing. The metrics look impossible for a NVDIMM form later this year. Literally we are supposed to actually buy the thing to get actual performance metrics for it? I don't think so.

    Its insane. This is probably the biggest marketing failure Intel has ever had. Don't they realize that nobody is being fooled by their crap specs?

    -Matt

    1. Re:Its rather exaggerated by freeze128 · · Score: 1

      Don't worry about the claims. Earlier articles said that all the xpoint memory was already spoken for by systems integrators for use in server class machines for at least the next year or so. Although Intel announces the SSD, it's still not available for purchase by the general public.

    2. Re:Its rather exaggerated by by+(1706743) · · Score: 1

      They say '12PB' of durability for the 375GB part but refuse to tell us how much overprovisioning they do. They say '30 drive writes per day' without tellling us what the warrenty will be.

      Those numbers (12.3PB) work out to be very nearly 3 years, for what it's worth -- perhaps (???) there's a 3-year warranty or something (or expected lifetime).

    3. Re:Its rather exaggerated by gravewax · · Score: 1

      ummm these are enterprise cards for server class machines, they aren't meant for the general public.

    4. Re:Its rather exaggerated by Anonymous Coward · · Score: 0

      > but refuse to tell us how much overprovisioning they do

      the article specifically describes effectively none, other than for ECC purposes.

    5. Re:Its rather exaggerated by Sarusa · · Score: 1

      That's wrong, and it's not your fault, it's the article's fault. They bought Intel's weaseling about this.

      They don't overprovision for /performance/ (which Intel will continually remind you), they overprovision for /endurance/.

      The only way they hit their stated life numbers on a 375GB drive is to put 448GB of XPoint memory on it, which you can see by opening one up.

    6. Re:Its rather exaggerated by Anonymous Coward · · Score: 0

      >Intels claims are rather exaggerated. Their claims have already been torn apart on numerous tech forums.

      Because people on tech forums always know more than the people who who actually design the process and products right?

    7. Re:Its rather exaggerated by blind+biker · · Score: 1

      But with potentially only 33,000 rewrite cycles per cell to failure that's seriously problematic. (And that's the best guess, since Intel won't actually tell us what the cell durability is).

      I can guarantee you it's not 33.000 R/W cycles - the only tech that would allow that is SLC, and practically nobody sells SSD based on SLC anymore. A few manufacturers sell highly overpriced SLC-based SD and microSD cards. Hell, nowadays you'll struggle to even find MLC-based SSDs (~10.000 rewrite cycles AT BEST). Every SSD manufacturer today uses TLC, which means 1000 R/W cycles per cell.

      --
      "The agriculture ministry is not in charge of Gundam" - Japanese ministry official.
    8. Re:Its rather exaggerated by Billly+Gates · · Score: 1

      Matt I respect your work on both Freebsd and Dragonfly but have you ever seen latency spikes from lots of small writes? My home PC has 2 raid 0 Samsung pros. Latency spikes go well over 1000 when running several Hyper-V or VMware workstation sessions easily. I am sure a server grade solution would be a little bit better.

      From what I have read is low latencies is the key and writes. Xpoint doesn't use blocks and does have endurance issues. 550,000 iops and lower latency is no joke on a SQL database or virtualization application server where that is always the bottleneck. Yes for home it's stupid but having a less than 100 MS latency means data can now be read

    9. Re:Its rather exaggerated by Anonymous Coward · · Score: 0

      375GB usable from 448GiB raw memory = 22% overprovisioning. For "ECC purposes". Riiight.

    10. Re:Its rather exaggerated by fgouget · · Score: 1

      >Intel's claims are rather exaggerated. Their claims have already been torn apart on numerous tech forums.

      Because people on tech forums always know more than the people who who actually design the process and products right?

      Maybe not but they may know more than the people writing the marketing brochures or the commercials selling the things. That said, the technology looks to be different enough from everything that came before that it's quite likely a lot of people are incorrectly applying irrelevant knowledge of how past products worked to this new one. It also feels like disk drives are a bad fit for the technology, but also the only one in the short term. Things will truly get interesting when/if they move to the 'large memory' / 'persistent memory' stage.

    11. Re:Its rather exaggerated by thegarbz · · Score: 1

      This is probably the biggest marketing failure Intel has ever had.

      This is a marketing failure. Not a market failure. Currently all we have to go buy is what Intel say. It won't be a market failure until a) the product is released and b) the product fails in the market.

    12. Re:Its rather exaggerated by thegarbz · · Score: 1

      Disregard that. I'm off for some much needed coffee.

    13. Re:Its rather exaggerated by EndlessNameless · · Score: 1

      Because people on tech forums always know more than the people who who actually design the process and products right?

      Probably not, but they will be a lot more honest than the marketing weasels who cherry-pick numbers to make the drive look as good as possible. Marketing weasels who don't even cherry-pick all the time---who sometimes just make things up.

      Both the press releases and the forum chatter should be taken with a grain of salt until in-depth independent reviews are available.

      But in the case that brochures and forums disagree, the company brochures are guaranteed to come with a strong bias.

      --

      ---
      According to the latest ruleset, this post should be modded as Vorpal Flamebait +5.
    14. Re:Its rather exaggerated by Tapewolf · · Score: 1

      I can guarantee you it's not 33.000 R/W cycles - the only tech that would allow that is SLC, and practically nobody sells SSD based on SLC anymore. A few manufacturers sell highly overpriced SLC-based SD and microSD cards. Hell, nowadays you'll struggle to even find MLC-based SSDs (~10.000 rewrite cycles AT BEST). Every SSD manufacturer today uses TLC, which means 1000 R/W cycles per cell.

      You're still talking about flash technology, as far as I can see... the point of Optane is that it's using this new phase-change stuff. Supposedly it would have a thousand times the write endurance, and be a thousand times faster than NAND flash (though I don't think they ever said whether it was SLC/MLC/TLC they were comparing to). It doesn't look like either promise has come true, though.

  6. SSD as cache by JustNiz · · Score: 1

    This seems like a particularly dumb idea. Wouldn't it be better to just add more RAM?

    1. Re:SSD as cache by darkain · · Score: 1

      SSDs for cache is extremely common in the storage server market. Check the section on L2ARC https://en.wikipedia.org/wiki/...

    2. Re:SSD as cache by Anonymous Coward · · Score: 0

      sure fine, find me 375GB of Enterprise level RAM for under $2,000. We have systems where I work with a 1TB of RAM, we could use more but for cost effectiveness we add an additional 1TB of SSD. sometimes tradeoffs are made, especially in storage based servers.

    3. Re:SSD as cache by AHuxley · · Score: 1

      Need to find a product thats much faster than SSD but not as expensive as a lot of RAM.

      --
      Domestic spying is now "Benign Information Gathering"
    4. Re:SSD as cache by Anonymous Coward · · Score: 1

      You can get 384GB(6x64) of ECC server ram for $5,202 on newegg...

      Is it more then 2K...yes Is it WAY faster then Xpoint at every metric...yes Does it ware out....no Do you basically have to think about it at all?...no For a 2K to 5K difference...the ram memory beats all...and it is not THAT much more expensive.

      If you want under 2K...what about a 2xM.2 pcie card(~$100-$150) with two 1TB Samsung PRO 950 M.2 cards for ~$1400? Run that in raid0 and you would probably be equal or better then the current Xpoint offering spec wise.....with 1.67Tb of more space/caching options. If you did it in raid 1 with a checksum file system...you would have fault tolerant cache with 3x the capacity for the price of this one card from Intel.

      I agree with everyone in here that Intel laid a stinker with this offering.

    5. Re:SSD as cache by sexconker · · Score: 1

      Are there hardware RAID controllers that support NVMe drives (U.2 or M.2 or direct PCIe), preferably with battery backup?
      I'm tired of being limited by SATA/SAS because hardware RAID is a requirement and I haven't seen anything reputable for the other options.

    6. Re:SSD as cache by Anonymous Coward · · Score: 0

      That's cute. We measure our SAN cache in the terrabytes, not gigabytes.

    7. Re:SSD as cache by enrique556 · · Score: 1

      While I agree in general, ECC server ram ain't ECC server ram.
      Finding a motherboard /system that supports that amount of ram can end up more expensive than the ram itself. And then you'll find that the 'board doesn't like those sticks you got from newegg, because server hardware tends to be a lot more picky in that regard. After you've dropped 20 grand on the rest of the system and returned that $5,000 ram kit, you could find that the only 384gb kit you can get working on your system costs three times as much.

    8. Re:SSD as cache by guruevi · · Score: 1

      Hardware RAID is ancient at this point, I wouldn't expect to see much further development in it. With SSD's there is no reason anymore to use hardware RAID or BBU's and hardware RAID controllers have been slower than the aggregate of even spinning disks for well over a decade now.

      --
      Custom electronics and digital signage for your business: www.evcircuits.com
    9. Re:SSD as cache by sexconker · · Score: 1

      RAID provides redundancy and speed. ESXi for example doesn't let you do RAID across multiple storage devices at a software level. My hardware RAID controller has 8 PCIe 3.0 lanes, cache, and battery backup. Yes, battery backup is still important. Yes, a RAM cache is faster than SSDs (though you'll wants to toggle the write cache policy). I don't live in pretend fairy land where SSDs never fail, and I don't shuffle shit off to a SAN/etc. device over network, fiberchannel, etc. because I want the performance.

    10. Re:SSD as cache by Billly+Gates · · Score: 1

      Go run a server? For a corporate file shared drive using this as a tier in server 2012 R2 or later will put the frequently accessed files on this greatly improving performance over accessing the slower mechanical disks in the raid. SQL databases can use this for stored procedures and frequently accessed data too as a cache from the slower SAN and latency

    11. Re:SSD as cache by TheRaven64 · · Score: 1

      You can get 384GB(6x64) of ECC server ram for $5,202 on newegg...

      So you can get 384GB of RAM for a bit more than 8TB of NVMe flash (not sure what the XPoint pricing is going to be).

      For a 2K to 5K difference...the ram memory beats all...and it is not THAT much more expensive.

      It's about 20 times as expensive per GB. You're arguing that the better latency and throughput of the RAM is going to outweigh the increased capacity of the NVRAM. That's by no means clear. If your working set fits entirely into that 384GB RAM cache, then the RAM will definitely be faster, but your working set is 1-4TBs (not that uncommon for a SAN device) then the RAM solution is going to be a lot slower than one with 128GB of RAM and 4TB of NVMe flash. For a smaller array, that $5K price difference is enough to replace all of the spinning rust disks with NVRAM, which will give you even better performance.

      If you want under 2K...what about a 2xM.2 pcie card(~$100-$150) with two 1TB Samsung PRO 950 M.2 cards for ~$1400? Run that in raid0 and you would probably be equal or better then the current Xpoint offering spec wise.

      Except that the one place that XPoint does seem to do a lot better than flash is in random reads, which is the main performance bottleneck for a cache device.

      --
      I am TheRaven on Soylent News
    12. Re:SSD as cache by Anonymous Coward · · Score: 0

      As much as people gripe about the cost of RAM it is the lack of address lines available in the processors that is the real problem followed closely by the address space. So unless you go with something like a SGI UV system that supports 64TB of shared memory you are basically limited single digit TB amounts.

      Any block based solution avoids those limitations

    13. Re:SSD as cache by Anonymous Coward · · Score: 0

      Ignore the idiots who don't understand the benefits of HW raid ;-)

      Broadcom had announced a RAID cone last year about this time but I haven't seen anything about availability let alone anyone building something with it yet.

      https://www.broadcom.com/news/press-releases/broadcom-delivers-first-nvme

    14. Re:SSD as cache by guruevi · · Score: 1

      I understand the concept behind RAID, but there is no way the slow ASIC with slow 1-4GB DDR2/3 RAM compete with the same drives directly attached to the CPU and potentially 100's of GB in DDR4 RAM. In your case your BBU RAID controller is a single point of failure, when your controller, its RAM and/or BBU fail, your file system will be corrupted so I wouldn't trust it with any 'write cache' policy unless you have a complement of them.

      A modern file system with SSD write caches should have at least 2 of them mirrored as well if you care about your data, so at least you know that whatever happens, the data fsynced is going to be there regardless of what happens, even if your controller goes up in smoke, you have a week-long power outage or you change hardware. You can get battery-backed RAM-based SSD's as well, they actually have been around for a really long time and they're about the same price as a high-end hardware RAID controller.

      --
      Custom electronics and digital signage for your business: www.evcircuits.com
    15. Re:SSD as cache by JustNiz · · Score: 1

      Good luck with that.

    16. Re:SSD as cache by sexconker · · Score: 1

      Are you kidding me? 2 GB of "slow" DDR3 blows away whatever SSD you're imagining in terms of both speed and latency. And the ASICs in RAID controllers can keep up just fine. They're typically designed to saturate all their internal links, with headroom.

      When the battery backup fails, nothing happens unless the server also loses power.

      Where are you getting servers with "100's of GB in DDR4 RAM" as a dedicated cache? Why would such amounts of cache matter when just a few GBs can provide a very low cache miss rate? How do you ultimately account for the lack of speed from running a single device compared to, for example, 4, devices in RAID 10? If you're advocating software RAID or various fake RAIDs, who is supporting it and what are you running on it? Can you boot from it?

      Yes, I suppose the RAID controller itself could fail. I've seen it once in my life in a server that was already decommissioned and resurrected to give it away to someone else.

      A modern file system with SSD write caches? WTF? I'm talking about the most popular "solution" in the server space - VMware ESXi. How do you set up software RAID in ESXi and use your "modern file system" as such? RAM-based SSD? You mean a fucking RAM drive? Those haven't been relevant for ages due to practical limitations on capacity and power, and of course the fucking cost. Maybe if someone goes back to them using HBM2 they'll be an option, but so far all I can conclude is that you're insane.

    17. Re:SSD as cache by WorBlux · · Score: 1

      RAM is expensive and a lot of it requires quite a bit on energy to keep refreshing,. Also it's not persistent so files in memory don't survive a reboot. This is especially true if you are working with data sets in the tens of gigabytes.

  7. PCI-E X2-X4 is a lot faster then sata. by Joe_Dragon · · Score: 1

    PCI-E X2-X4 is a lot faster then sata.

    1. Re:PCI-E X2-X4 is a lot faster then sata. by Anonymous Coward · · Score: 0

      Well that ruins my idea for a SATA graphics card.

  8. /. Yesterday's News Today! by Anonymous Coward · · Score: 0

    That's all. With the numerous changes of hands and lack of focus, /. has become a non-player in the space of "news." Turn off the auto-renew on the domain and die with a bit of dignity left.

    A wise man once said;
    You've got to know when to hold 'em
    Know when to fold 'em
    Know when to walk away

    1. Re:/. Yesterday's News Today! by sexconker · · Score: 1

      Know when to run
      You never count your money
      When you're sittin' at the table

  9. STT-MRAM or bust by WaffleMonster · · Score: 1

    XPoint is well... pointless. It can't compete with MRAM and by the time it matures enough (If it matures enough) to substitute flash in any kind of significant way MRAM is likely to have already taken over.

    MRAM has effectively infinite read/write endurance, high density and performance characteristics of static ram.

    XPoint even if executed perfectly has only a narrow window in which it can hope to remain relevant.

    1. Re: STT-MRAM or bust by Anonymous Coward · · Score: 0

      Looks like Intel is also working on MRAM
      http://seekingalpha.com/article/4051541-suerte-de-capote-intels-cannonlake-leaked-patent

    2. Re: STT-MRAM or bust by Anonymous Coward · · Score: 0

      Looks like Intel is also working on MRAM
      http://seekingalpha.com/articl...

      Intel has worked on everything. Intel knows what works and what doesn't. Just as importantly, Intel knows what is mass manufacturable and what isn't.

    3. Re:STT-MRAM or bust by TheRaven64 · · Score: 2

      The first article I read that promised MRAM real soon now was around 2008. I'm not holding my breath.

      --
      I am TheRaven on Soylent News
    4. Re:STT-MRAM or bust by Anonymous Coward · · Score: 0

      The first article I read that promised PRAM real soon now was around 2006. Guess what XPoint is using as the storage cell...

    5. Re:STT-MRAM or bust by cheesybagel · · Score: 1

      There's MRAM available for sale right now. Everspin sells it:
      https://www.everspin.com/

      The problem is it has less density than DRAM and it's a lot more expensive. It does have better latency though, so it could be used as a kind of persistent last level cache.

  10. how do these stack up against fusionIO Drives? by Anonymous Coward · · Score: 0

    remember Fusion IO drives, those used to be B1tch quick, but had a habbit of burning up..
    I wonder how these stack up with regard to performance against each other?

    Hm,m..

  11. Off topic by justthinkit · · Score: 1

    Is there any way we can banish xx.xxx (or even worse, xx xxx) notation?

    It is incredible that the world doesn't have a single standard for numbers (not counting scientific notation, which is something different, and btw rarely used).

    How are we supposed to differentiate 33.000 (i.e. 33 thousand) from 33.000 (33, to an accuracy of 3 decimals)?

    We can go to the moon, but can't state numbers unambiguously. Mind officially blown...

    --
    I come here for the love
    1. Re: Off topic by Anonymous Coward · · Score: 0

      Idiot. This is callled localization. The fact this blows your mind means there isn't much mind. Things are different in other countries. Language, foods, clothing, how numbers are represented. Do a little reading you dumb fuck. You have wasted everyone's time who read your crap just to get by it.

      And now I have too.