BalAtWork, you are still missing some information.
<< Cquin: I did not know the details of the ramdrive so that is educational.
But if you look at the battery backed ramdrive for 1500 that Uuplaku mentioned,
you see that it IS being done already.
<<
It has "been done" for years, there were battery backed ramdrives around
back when a 50Mhz 486 was considered a blazingly fast machine.
Those drives cost about 10x as much then, so the prices have come down,
but for the same amount of money you could buy a kickass SCSI controller
and Seventy-Five times as much storage in 15000rpm drives.
<< I understand the current system uses 16bit, or even 32 bit for other software.
But I DO have to disagree with you on the statement that this is not needed. >>
I never said it was not needed, Hell I'd love to have a cheap Solid-State Hard
Drive to boot my system from. They should have been building that technology
into motherboards as far back as 1995. But (not a slam)
the way you would try to put a RAM-drive together does come across as a bad idea.
<< Keeping the information in the RAM would not occupy any CPU cycles to maintain
the data there. >>
That would be true if it was DATA but a RAM drive is used as
STORAGE which opens up a different set of issues. For it to work
right, the OS has to use the Ramdrive.sys driver as the interface between
it and the data it is looking for; in much the same way that internal
support for SCSI, USB, Firewire and even IDE comes about thru a custom
driver for the OS. But in this case when a data request is passed thru
the driver, to the controller, and then to the drive itself; what is
really happening is that the CPU is forced into double duty both as the
messanger of the data request, and as the controller to pass commands
on to the device itself. You would be getting a similar effect as if
you had turned off DMA for your IDE devices, the CPU would have no
other device that it could pass some of the workload on to.
Add to that the hundreds of background requests that an OS like Windows
makes to the filesystem just to make sure files it might need are
around, and you start to get a picture of how much overhead you put
on the CPU, when it could probably be more efficiently used to boost
your 3dbench scores.
Solid-State drives or "RAM-Disk on a card" solutions also come with
their own controllers, or are usually built as SCSI devices to avoid that
exact problem above.
<< As for todays parts being fast enough...BLAH That is never
true as is evident by At100 AT 133 etc... coming out, heck by the fact a
RAMdrive IS being made. >>
ATA-133 was more to break the 128Gig barrier than to boost speed.
The only time dedicated RAM-Drives or Solid-State drives have useful
is when it saves or makes a company more money to use such a device
than it costs them to buy and install them in the first place.
And even then, the drives are uses as caching buffers for larger
hard drive arrays, or to provide fast turnaround for mission critical
installations.
Whitedogs point is that it is more efficient to use the majority of
your memory as RAM, and not cripple your system by taking away from
the OS its primary resource.
<< BUT I would gladly take a 5 minute boot to have a computer run without ANY
harddrive noise, seek times, etc.....
<<
I'm willing to bet your system has more than 2Gigs of hard drive space on it.
So you'd use 5 min to boot, have 1 pure minute of quiet, and then go back to
the harddrive noise, seek times, etc. to get acesss to the rest of your stuff.
I'll take my under one minute boot time, along with the 100+ Gig of drives
that I can hardly hear over the sound of my fans, and try to save my money for
the DVD burner I want, or even wait for the day when holographic storage
comes along to give me the best of both worlds.
<< I guess they key is that this can be done NOW with some software to achieve
the results of a 1500 dollar drive being made. >>
Nope, nice to think so, but there is a reason those cards still cost
several times the value of the memory built onto them.
<< Whitedog, you said thinking outside the box was good, well DO IT THEN. >>
I'll throw that one back in your court, and ask you to consider factors beyond
just the speed of RAM vs that of the Hard drive.
<< Just imagine if that RAM could be powered 100% of the time if the MB was
designed correctly, we would ALL be using RAM drives now!
<<
Would we? Based on what? DRAM? EDO? SDRAM? RAMBUS? DDR?
Every few years when the idea comes up, somebody comes up with a whole new
type of RAM to build the motherboards around, and they all get re-designed
to accomodate it.