Skip to main content

Huge amounts of data storage on water?



Water? H2O? Is it possible? Well this Drexel Physics professor thinks so!

RAM is necessary in a computer because it stores information for programs that are currently running. As this news release was written, RAM stored the words in a file. Because RAM can transfer files faster than a hard-drive, it is used to handle running programs. However most RAM is volatile, and if the computer loses power all the information in RAM is lost. This is not the case with ferroelectric memory.

Ferroelectric memory is non-volatile, so it is entirely possible for files to be stored permanently in a computer¹s RAM. Applying nano-wires and the new stabilization method to existing ferroelectric RAM would deal a double blow to hard-drives in size and speed.


And that would take the storage world (and the Storage giants) into a total different battle arena. Imagine (but again I did muse lightly about it on my very first article-- Hmm how time flies). Plugging in modules to your hyperactive-hyperavailable applications (I think we should start calling every application we develop as an appliance). And when I say that I don't mean a physical appliance like this from Google but a "Virtual Appliance which needs no intervention from anyone of us. Users OR adminstrators/developers alike.

Build an appliance, deploy it with gobs of Ferroelectric memory with only modules (additional Ferroelectric memory) which you plug in to scale up/scale down your applications...oops sorry appliances :-)

Neat, I've been watching this too but I'll watch professor Spanier even more closely.
Labels:

Comments

Post a Comment

Popular posts from this blog

Security: VMware Workstation 6 vulnerability

vulnerable software: VMware Workstation 6.0 for Windows, possible some other VMware products as well type of vulnerability: DoS, potential privilege escalation I found a vulnerability in VMware Workstation 6.0 which allows an unprivileged user in the host OS to crash the system and potentially run arbitrary code with kernel privileges. The issue is in the vmstor-60 driver, which is supposed to mount VMware images within the host OS. When sending the IOCTL code FsSetVoleInformation with subcode FsSetFileInformation with a large buffer and underreporting its size to at max 1024 bytes, it will underrun and potentially execute arbitrary code. Security focus
Post a Comment
Read more

Splunk that!

Saw this advert on Slashdot and went on to look for it and found the tour pretty neat to look at. Check out the demo too! So why would I need it? WHY NOT? I'd say. As an organization grows , new services, new data comes by, new logs start accumulating on the servers and it becomes increasingly difficult to look at all those logs, leave alone that you'd have time to read them and who cares about analysis as the time to look for those log files already makes your day, isn't it? Well a solution like this is a cool option to have your sysadmins/operators look at ONE PLACE and thus you don't have your administrators lurking around in your physical servers and *accidentally* messing up things there. Go ahead and give it a shot by downloading it and testing it. I'll give it a shot myself! Ok so I went ahead and installed it. Do this... [root@tarrydev Software]# ./splunk-Server-1.0.1-linux-installer.bin to install and this (if you screw up) [root@tarrydev Software]# /op
Post a Comment
Read more