Comments on: MySQL Database Sizes http://www.thiswebhost.com/blog/2009/08/20/mysql-database-sizes/ Keep up to date with ThisWebHost Thu, 05 Jan 2012 10:23:59 +0000 hourly 1 http://wordpress.org/?v=3.3.1 By: Jules http://www.thiswebhost.com/blog/2009/08/20/mysql-database-sizes/comment-page-1/#comment-5232 Jules Fri, 21 Aug 2009 19:18:20 +0000 http://www.thiswebhost.com/blog/?p=99#comment-5232 @Darfuria - That's (hopefully) the point :) The limitations should affect only a very very small number of people, but serve to ensure that the others get the best possible performance they can. We don't want anyone to be negatively impacted by this, but rather cause them to become proactive in ensuring that their databases are pruned of old and possibly obsolete data regularly. Most of the time it's silly things like a forum that can contain many tens of thousands of "Invalid login" entries that simply need to be emptied. In regards to the opimisations, it's really hard to say what the difference would be in terms of performance. On the individual databases, we don't do much optimisation at all. Weekly we optimise all tables on every database to reduce slack space (this helps to keep your database sizes down and improves performance slightly) and we do have checks looking for poorly utilised indexes and will change them to be more efficient if needs be. The real performance gains come from the MySQL configuration itself, and unfortunately it's something not many people know how to (or bother to) optimise correctly. Maybe I'll try and get together some benchmarks for comparison ;) In the meantime, here's what someone said when migrating from an expensive VPS: http://www.thiswebhost.com/forums/index.php/topic,8.msg57.html#msg57 @Darfuria – That’s (hopefully) the point :) The limitations should affect only a very very small number of people, but serve to ensure that the others get the best possible performance they can. We don’t want anyone to be negatively impacted by this, but rather cause them to become proactive in ensuring that their databases are pruned of old and possibly obsolete data regularly. Most of the time it’s silly things like a forum that can contain many tens of thousands of “Invalid login” entries that simply need to be emptied.

In regards to the opimisations, it’s really hard to say what the difference would be in terms of performance. On the individual databases, we don’t do much optimisation at all. Weekly we optimise all tables on every database to reduce slack space (this helps to keep your database sizes down and improves performance slightly) and we do have checks looking for poorly utilised indexes and will change them to be more efficient if needs be.

The real performance gains come from the MySQL configuration itself, and unfortunately it’s something not many people know how to (or bother to) optimise correctly. Maybe I’ll try and get together some benchmarks for comparison ;) In the meantime, here’s what someone said when migrating from an expensive VPS:

http://www.thiswebhost.com/forums/index.php/topic,8.msg57.html#msg57

]]> By: Darfuria http://www.thiswebhost.com/blog/2009/08/20/mysql-database-sizes/comment-page-1/#comment-5193 Darfuria Fri, 21 Aug 2009 10:21:42 +0000 http://www.thiswebhost.com/blog/?p=99#comment-5193 I think it's a great idea - although I can't see the limitations ever affecting me. I would be interested to see some differences in performance between two databases that are exactly the same - one that has been optimised by you, and one that hasn't. I think it’s a great idea – although I can’t see the limitations ever affecting me.

I would be interested to see some differences in performance between two databases that are exactly the same – one that has been optimised by you, and one that hasn’t.

]]>