Who /ramdisk/ here?
>Installed Fallout 4 on it, because loading times were still bad even on SSD
I just woke up, okay?
>ramdisks that just save and load from a hdd during shutdown
that's what mine does. using Gilisoft Ramdisk, saves to .img, saves on shutdown and mounts on startup, and I have set it to write any changes to .img every 10 minutes.
What is the fucking point. The OS uses unused memory as a disk cache. If you want an entire folder in memory just scan over all the files reading them, it'll take just as long as loading a ram disk image, except won't be in the way when applications actually need to use RAM, and you're not forced to do it to boot up.
Ramdisks are the fucking future!
Still sucks ass a 32 gig config costs like $200+. I hope prices abate soon.
What would be nice is a motherboard with native ramdisk support. For example some 10000 mAh battery that keeps the memory running so even if power gets cut out, it still retains everything and you don't have to load anything.
SSDs nullify this problem though. Just save ram disk image to an SSD and load that every time you boot. SSDs can transfer an unrealistic 32GB ram disk image to RAM in a minute or two.
It's not about how fast you get it into the ram, it's how quickly you can manipulate large amounts of data without having to pull and push from the hard drive while manipulating it.
>when applications need to use the ram
The applications are totally inside ram at this point, and are more directly read from and written to.
The ram interface is at least an order of magnitude faster than the most capable ssd interface, whether sata3.0 or pci-e
that was a tremendous lie.
companies like amazon and shitheads at newegg have literally, HUNDREDS OF THOUSANDS of ramsticks, but they all agreed to drastically increase the price, becuase why not?
and thus we have the stupidly over priced hardware of today.
>one block of ram becomes corrupt
>say goodbye to all your work
>having to waits twenty minutes between shutdown and power on
toppest kek, at least use an SSD...
Once files are in the disk cache then they are entirely in RAM. After that the only disk operations required are fully buffered writes (i.e. they happen in the background and don't block the application).
Disk cache /= system ram
You'd still be exchanging data between the hard drive and ram before and after computations, and that takes more time than just keeping all data on the system ram, which is what a ram drive does
But the disk cache is in RAM? Just like a ram disk is in RAM.
Once it's in RAM (i.e. has been read and not pushed back out yet) you no longer have to read it again. It takes zero more time than a ram disk, but it's a less retarded way of doing things for anything not 100% temporary.
Unless you're running Windows XP, your operating system isn't retarded, and using a ram disk for speed is pointless memejerking.
Experiment time!$ time cat /usr/lib/i386-linux-gnu/* > /dev/null
$ time cat /usr/lib/i386-linux-gnu/* > /dev/null
Wow, it's like my operating system magically put the files in some kind of invisible "ram disk" after the first time I read them!$ sudo mount -o size=512M -t tmpfs none ./memedisk
$ sudo chown me:me memedisk/
$ sudo cp /usr/lib/i386-linux-gnu/* memedisk/
$ time cat memedisk/* > /dev/null
Damn look at those epic ricer speed gainz on my memedisk. Sure glad I'm not letting my RAM go to "waste" and filling it up with memedisks so that pesky, untrustworthy operating system disk cache doesn't try and speed things up on its own.
Stop exaggerating. Even an idle desktop (assuming a modern haswell/skylake i3/i5) wastes ~10 watts with the screen off. That's a whopping 1 dollar each month of wasted electricity. I guess that's still not a lot though.
Disk cache is not in system ram, it is on a small ram chip inside the hard drive.
When data is sent from the hard drive to system ram, the same communication route is used whether the data is coming from the spinning disk or the cache.
The cache only improves transfer speed incrementally because the disk doesn't move when the desired data is already in cache. However, the data must still be sent from the cache to system ram in order for it to be processed.