Earlier quoted context omitted.
How is this different than IBM's single store model? Memory and disk are addressed as one with hardware providing the protection needed in case of component or system failure. Unless your writing at the machine level I really do not see the need for most programmers to ever concern themselves with storage, that should be the work of the underlying machine code and/or OS.
if ram and permanent storage becomes the same, in instance, you wont need to "open(" a file, just to point to the memory location of it.
Bringing SSD Performance to the DIMM form factor
181–190 of 205 posts
Re: Bringing SSD Performance to the DIMM form factor
#182I can't wait to see the programming paradigm of memory vs permanent storage begin to blur in the next 5 or so years. It's going to make some major assumptions about how you program stuff change quite significantly and it's really exciting.
IBM went all the way with this in the AS/400 back in the 80's. Single level store - RAM and disk were unified storage. with no ability for a programmer to tell the difference (RAM was purely and operations problem).
I really recommend Frank Soltis' Inside the AS/400 if you are interested in computer architecture and virtualization.
Re: Bringing SSD Performance to the DIMM form factor
#183I can't wait to see the programming paradigm of memory vs permanent storage begin to blur in the next 5 or so years. It's going to make some major assumptions about how you program stuff change quite significantly and it's really exciting.
Memristors (long promised and still not quite here) also bring together the ideas of long-term and short-term memory into one and, in future incarnations, even promise to bring computation and storage together.
I just assumed they are integrating it into their new super computer
Re: Bringing SSD Performance to the DIMM form factor
#184Earlier quoted context omitted.
And AMD is aiming towards a shared GPU/CPU architecture too.
I'm really excited for shared RAM between GPU and CPU. At the moment GPU acceleration is limited by the meagre amount of VRAM on most desktop cards. I would love to be able to do GPU programming with a 32+GB RAM pool.
Re: Bringing SSD Performance to the DIMM form factor
#185You can tell SanDisk's performance numbers do not add up and that they are likely misrepresenting the true performance of their device. (Those red asterisks next to the numbers correspond to a footnote that is conveniently missing from the page...) A "read latency of 150usec" translates to maximum possible read IOPS rate of 1/150e-6 = 6.67K (with one outstanding I/O). But they quote a "random read IOPS of 140K". That…
Maybe you can submit more than 8 queued requests to the controller and have them stream back at the full DDR3 data rate. Maybe it's not actually addressable as RAM, it just uses the DDR3 interface as a communication bus.
Re: Bringing SSD Performance to the DIMM form factor
#186I don't quite understand. Does this act like a stick of memory or an SSD? Is it just using the memory controller as a super fast parallel bus? If it does act like normal memory, what happens at reboot?
Answer is there in FAQ. Written data is not lost on reboot, so basically you can mount it as a `ramdisk` partition and use that as data directory for your database. I have used this approach in past to speed up large test suite of a web application, except it required restoring from some sort of backup on reboot. Which won't be necessary in this case.
Re: Bringing SSD Performance to the DIMM form factor
#187Earlier quoted context omitted.
I don’t disagree with you one bit, but I find it funny that you say: “we can't currently break them, so tradeoffs will always exist.” :) (That “currently” is just a weasel word, but this being the Internet I understand why you put it there)
It is highly probable that we will discover memory that is better than current memory in every relevant metric (I suspect this is what you think you are claiming). It is highly improbable that this new technology cannot be optimized in any relevant metric by trading off optimality in a different metric (this is what you are actually claiming).
Re: Bringing SSD Performance to the DIMM form factor
#188Earlier quoted context omitted.
I'm really excited for shared RAM between GPU and CPU. At the moment GPU acceleration is limited by the meagre amount of VRAM on most desktop cards. I would love to be able to do GPU programming with a 32+GB RAM pool.
Using the system RAM is how a lot of on-board budget graphics chips used to (still do?) work.
Re: Bringing SSD Performance to the DIMM form factor
#189Earlier quoted context omitted.
Well, if you have plentiful persistent RAM an application could easily "suspend" itself (on shutdown for example), and then resume running at a later point in time. The code would not have to think about this, since the entire state is just snapshotted. It's basically what machines do now when they "hibernate", except more effecient and could even happen if the power got cut. Additionally I suppose your variables cou…
Can't wait for the persistent memory leaks!