On 8 Feb 2004, at 19:37, Mark Hazen wrote:
*snip*
Here's my problem: I've got a bunch of tables with hundreds of millions of
rows in them. Every night, I delete about couple million rows and then run
millions of searches on these tables.
What should I worry about more? A sorted index or a data file with no deleted rows in it?
I don't mind running either OPTIMIZE TABLE (which apparently rebuilds everything and sorts it) or just the myisamchk to sort the index. Does anyone know which one might get me more mileage?
What's the nature of your query?
If it's using an integer index and that's what your searching on, then having
it physically sorted is a Good Thing. If you're table-scanning your
main table, you're toast anyway. Finding ways of making that faster is the
way to go, maybe partitioning your data into "small, fixed width, fields I
care about" and "other stuff" is the way to go?
-- Dave Hodgkinson CTO, Rockit Factory Ltd. http://www.rockitfactory.com/ Web sites for rock bands
-- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
