RE: Partial Row Reads? - Dathan Vance Pattishall - com.mysql.lists.mysql

8 messages in com.mysql.lists.mysqlRE: Partial Row Reads?

From	Sent On	Attachments
Ken Gieselman	21 Oct 2004 01:11
Ken Gieselman	21 Oct 2004 06:03
Dathan Vance Pattishall	21 Oct 2004 12:59
SGr...@unimin.com	21 Oct 2004 13:40
Harrison	21 Oct 2004 17:32
Harald Fuchs	22 Oct 2004 04:17
Ken Gieselman	25 Oct 2004 00:23
Tom Cunningham	25 Oct 2004 04:23

Subject:	RE: Partial Row Reads?
From:	Dathan Vance Pattishall (dat...@friendster.com)
Date:	10/21/2004 12:59:48 PM
List:	com.mysql.lists.mysql

DVP

---- Dathan Vance Pattishall http://www.friendster.com

-----Original Message-----

So, is there a faster way to insert/index the data? Would a different table or index type improve performace?

Use Load data from infile .. IGNORE ... u might get a better insert speed increase. A different table and a different index / compound index would improve performance from an insert to a select perspective.

above query, according to explain), the current behavior makes it reads 29548800 complete rows, which is 275.4 GB of data to read, even though the desired return is about 1/2500th of that (112.7 MB).

If a range covers more then 30% of the table a table scan is performed, instead of an index scan.

Any/all suggestions, comments, even flames are welcoome :) Thanks in advance!

ken

Look at some my.cnf options. You can tell mysql to use keys more often the table scans with a var called max_seeks_keys=100 // something like that

========================================================================== = "Diplomacy is the weapon of the Civilized Warrior" - Hun, A.T.

Ken Gieselman kgie...@endlessknot.com System Administrator http://www.endlessknot.com/~kgieselm Endlessknot Communications http://www.endlessknot.com ========================================================================== =