Re:Ask HN: Dealing with a huge MySQL database - help
by webvet on Sunday September 08, 2013 @11:34AM
(#6349032)
Yes, we enable slow query logs from time to time, look at those and try to optimize for those. MyISAM tables.
We've been cycling frequently (and painfully) through (2) (and less frequently through (1)) for the best part of three years now, so please don't accuse us at least of looking for a quick fix :)
Re:Ask HN: Dealing with a huge MySQL database - help
by gmuslera on Sunday September 08, 2013 @12:32PM
(#6349228)
With MyISAM tables you could have integrity problems. And if you are mixing innodb and myisam you are splitting buffers memory that well could go to just one kind (i.e. most memory for innodb) if you switch to that.
If innodb is slow in insertions, you could try using TokuDB as storage engine, that is pretty fast in that and have a bunch of advantages.
And if you are using MyISAM for some particular feature (i.e. full text indexing) MySQL 5.6 already have it in innodb, or you can separate that search to a sphyinx server.
Re:Ask HN: Dealing with a huge MySQL database - help
by webvet on Monday September 09, 2013 @04:56AM
(#6352434)
Thanks. We'll check out TokuDB.
Re:Ask HN: Dealing with a huge MySQL database - help
by webvet on Sunday September 08, 2013 @06:29PM
(#6350691)
> 150GB and 100M records is not huge, not even close.
Close to what, if I may ask?
Re:Ask HN: Dealing with a huge MySQL database - help
by petervandijck on Sunday September 08, 2013 @07:41PM
(#6351020)
Agree. 1B rows is big. 100B rows is huge. 100M rows is large, but totally doable.
Are these MyISAM tables or InnoDB?
150GB and 100M records is not huge, not even close. You are looking for a quick fix and there isn't one. You need to start with (2).