MySQL Forums
Forum List  »  Newbie

Re: Very long query doubt... (Monster query...)
Posted by: Rick James
Date: March 31, 2009 08:30AM

261MB for data, 69MB for index -- currently.
419MB for key_buffer -- this is caching for indexes (not data). This is arguably too big for a 1GB machine; suggest 200M. (I doubt if you see any performance change at the moment.)

The 30% will shrink as you get more data. This will lead to it deciding to use the index. But, again, I don't expect much change in performance (and I can't predict whether it will get slower or faster).

A future problem... As your data increases in size, it will become less cacheable. This will lead to being I/O bound. If you aren't happy today with the performance, you really won't be happy then. Consider getting more RAM before long.

Perchance, can you make a weekly summary table from the data you have? That might make this query run 7x faster, at the cost of an expensive weekly job.

Options: ReplyQuote

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.