Re: how to estimate a hardware server's requirement for MySQL database server?
Posted by:
Rick James
Date: September 18, 2014 05:06PM
> the database volume will be 2~3TB
Since it is impractical to have enough RAM to cache it all, then have as much RAM as you can afford. Then set innodb_buffer_pool_size to 70% of it. At some point, adding more RAM gets into "diminishing returns".
> applications will query and generate reports.
Data Warehousing? Look seriously into "summary tables". Provide more about your schema, etc, and we can discuss this further.
> it will be 50+GB data loaded into DB every day
Let's also look at how you will be doing the loading -- loading that fast will be seriously challenging.
> data are saved in FC storage.
What is FC?
> CPU needed for MySQL server ?
A single MySQL connection will not use more than one CPU core. Current machines have lots of cores. So, don't spend extra money on more cores.
Hmmm... 50GB/day means 2TB in 40 days?? Sounds like you will be purging data after maybe 30 days? If so, be sure to PARTITION BY RANGE(TO_DAYS(...)) and have a daily task to DROP the oldest PARTITION and create a new one. If this sounds reasonable, I can give more details.
Subject
Written By
Posted
September 10, 2014 12:54AM
September 10, 2014 01:15AM
September 18, 2014 03:09AM
Re: how to estimate a hardware server's requirement for MySQL database server?
September 18, 2014 05:06PM
September 18, 2014 05:10PM
Sorry, you can't reply to this topic. It has been closed.
Content reproduced on this site is the property of the respective copyright holders.
It is not reviewed in advance by Oracle and does not necessarily represent the opinion
of Oracle or any other party.