3 ms·
One of the most actively-used databases at my company is about 1GB in size and grows at about 100MB/month. It is a Windows-based DB and is very heavy on the rea
by chime 17y ago
One of the most actively-used databases at my company is about 1GB in size and grows at about 100MB/month. It is a Windows-based DB and is very heavy on the reads. I installed SuperVolume http://www.superspeed.com/desktop/supervolume.php http://www.superspeed.com/desktop/supervolume.php on the DB server and created a 4GB disk partition to store the DB files. SuperVolume mirrors the entire 4GB disk partition in RAM and works flawlessly and transparently.
I was going to get an SSD for performance enhancement but I don't much see a reason to do that anymore. All the reads happen at the speed of RAM and writes are delayed and non-blocking. Nested queries that used to take 15 minutes now take 45 seconds.
Right now the speed issues we have are solely due to unoptimized algorithms and not due to hardware limitations. This is a wonderful spot for a coder to be in because there is so much room for improvement now. If you have Windows systems serving files and data on slow systems, I would highly recommend giving SuperVolume and its related apps a shot before investing in expensive SSDs.