The really exciting part here, to me, is the idea of fabricating large amounts of nonvolatile memory on top of a CPU. Modern processors already spend a huge amount of their time waiting on memory, and a great amount of power trying to hide that memory latency. If these guys can lower memory latency dramatically -- and it looks like they can -- computers would get a lot faster.
I watched the whole 47 minutes of that talk on youtube, and it is actually really good. I have no qualifications in this field, but the talk is full of challenging ideas. You can skip reading the article.
The no more hard drive and persistent ram thing should be really interesting. Completely change how we do things.
Also, application specific processing... writing instruction sets for each application will be really interesting. Cell processing et al will be a thing of the past.
Here we have HP on the verge of profoundly transforming our industry and a CEO (who should be aware of this) wanting to turn the company into an SAP, because that's the future...
I hope Meg Whitman does better than Leo Apotheker. Shouldn't be hard.
But will Meg take it in the right direction either? Her experience is consumer-facing... I hope there is an empowered VP or 2 who will make that initiative a success.
What are the implications for back end development? Will this greatly reduce server complexity (need for redundancy)? Could AWS just give you a machine in the cloud, and you wouldn't need to worry about databases and database backups and so on, you could just keep all your data locally in natural data structures?
This would not necessarily affect back end development as you would still want high availability for the application by using an active-active setup across two availability zones in EC2.
With regard to your question on data structures, yes - they would have to change. MySQL and most other databases use b-trees since they were meant to live on disk. Just running MySQL on memsistor-backed storage would result in a considerable waste of CPU and storage capacity (b-trees are not very compact).
Running a database like MemSQL on memsistors would make the most sense since it uses data structures meant for DRAM.
I wonder how these theoretical projects will survive in an HP that is only concerned with how much profit each project makes to appease shareholders...
The bad side-effects of this memory technology: you can't just power-off your computer to hide your current activity; decrypted passwords in memory still will be readable after shutoff.
This is silly. Just because memory is non volatile storage doesn't mean the OS can't do reasonable things like clearing out some state as it goes to sleep.
The specific quote was "We’re planning to put a replacement chip on the market to go up against flash within a year and a half"
and "We have a lot of big plans for it and we're working with Hynix Semiconductor to launch a replacement for flash in the summer of 2013 and also to address the solid-state drive market"
June 2013 is twenty months away, so "a year and a half" is a very reasonable approximation, which it looks like the article writers then approximated again as "18 months"
It's an estimate not an exact length of time. 18 months takes us to April 2013, so maybe they rounded April into "summer" or maybe they rounded 20 months to the nearest .5 of a year. Or maybe they class April as summer anyway.
It won't disappear. It could be split, close some sites, change leadership again, etc. but it won't simply cease to exist. The existing infrastructure itself is worth too much.
[+] [-] uniclaude|14 years ago|reply
[1]:http://eetimes.com/electronics-news/4229171/HP-Hynix-to-laun...
[+] [-] hornokplease|14 years ago|reply
[+] [-] pjscott|14 years ago|reply
[+] [-] TheEzEzz|14 years ago|reply
[+] [-] plasma|14 years ago|reply
http://www.youtube.com/watch?v=bKGhvKyjgLY&sns=em
[+] [-] TheEzEzz|14 years ago|reply
"So, I mean, we're all of a sudden talking petabits of memory in a square centimeter device. What can you do with that? Interesting to think about."
[+] [-] speleding|14 years ago|reply
[+] [-] bluehavana|14 years ago|reply
Also, application specific processing... writing instruction sets for each application will be really interesting. Cell processing et al will be a thing of the past.
[+] [-] lordmatty|14 years ago|reply
[+] [-] calebmpeterson|14 years ago|reply
I'm especially curious how Rich Hickey's approach to state, time, and identity in a functional language fit in?
[+] [-] rbanffy|14 years ago|reply
I hope Meg Whitman does better than Leo Apotheker. Shouldn't be hard.
[+] [-] vnchr|14 years ago|reply
[+] [-] bane|14 years ago|reply
[+] [-] palish|14 years ago|reply
[+] [-] TheEzEzz|14 years ago|reply
[+] [-] ericfrenkiel|14 years ago|reply
With regard to your question on data structures, yes - they would have to change. MySQL and most other databases use b-trees since they were meant to live on disk. Just running MySQL on memsistor-backed storage would result in a considerable waste of CPU and storage capacity (b-trees are not very compact).
Running a database like MemSQL on memsistors would make the most sense since it uses data structures meant for DRAM.
[+] [-] sliverstorm|14 years ago|reply
[+] [-] dmix|14 years ago|reply
As a consumer, I'm indifferent to who does it. As long as it gets out.
[+] [-] aheilbut|14 years ago|reply
[+] [-] rsanchez1|14 years ago|reply
I wonder how these theoretical projects will survive in an HP that is only concerned with how much profit each project makes to appease shareholders...
[+] [-] nwatson|14 years ago|reply
[+] [-] jasonwatkinspdx|14 years ago|reply
[+] [-] jeroen|14 years ago|reply
[+] [-] themgt|14 years ago|reply
and "We have a lot of big plans for it and we're working with Hynix Semiconductor to launch a replacement for flash in the summer of 2013 and also to address the solid-state drive market"
June 2013 is twenty months away, so "a year and a half" is a very reasonable approximation, which it looks like the article writers then approximated again as "18 months"
[+] [-] corin_|14 years ago|reply
It's not like those two times are way different.
[+] [-] dhughes|14 years ago|reply
[+] [-] viraptor|14 years ago|reply
[+] [-] DasIch|14 years ago|reply
[+] [-] bvi|14 years ago|reply