Why flash memory for MySQL?

By jrudisin - Last updated: Saturday, June 12, 2010 - Save & Share - 2 Comments

Hard drives spin slowly.
Users wait, unhappy, sad.
MySQL needs flash!

Posted in CEO Jerry Rudisin, MySQL • Tags: , Top Of Page

2 Responses to “Why flash memory for MySQL?”

Comment from Den
Time June 24, 2010 at 4:48 AM

Does that mean you can forget the “tuning-for-fitting-in-memory” issue?

Comment from jrudisin
Time June 24, 2010 at 9:42 PM

Not at all — if your data is small enough to fit in memory. If you can fit your entire databse in DRAM you’ll get the best performance. But as databases get big, it is prohibitively expensive to by enough DRAM to keep the entire database in memory. Flash memory is vastly cheaper than DRAM as well as much more energy-efficient. Schooner’s MySQL Appliance comes in configurations of 512 GB and 1 TB of flash memory. And we have a unique balanced system approach in which we have tuned the MySQL + InnoDB software to optimally exploit flash memory, DRAM, multi-core processors, and high-speed interconnections among machines. That’s why we outperform other flash-based solutions by far, and even outperform, for example, expensive Cisco servers with 384 GB of DRAM.

Write a comment