It depends also on how much speed you want. Generally primary-key or indexed-key queries will be quite fast, O(sqrt(N)) speed. However if you are doing range queries that will be slower.
130M rows is a large-ish table by most measures, depending on your row size and result set size, you might be hitting machine limitations. On Jan 14, 2008 7:08 PM, Gerald Timothy Quimpo <[EMAIL PROTECTED]> wrote: > On Mon, 2008-01-14 at 17:46 +0800, joebert jacaba wrote: > > Please give some pointers to speed up query to a 130 million ++ rows > > mysql table. This table has 5 columns. A primary key, an account code, > > an OR number, a date and a status id. I am currently indexing the > > table on the account code. > > what's the query? generally, you'll need an index on the column(s) > in the where clause, although exactly what you're doing in the where > clause can make a difference too and sometimes just having an index > on the columns used in the where clause might not always help. -- Orlando Andico +63.2.976.8659 | +63.920.903.0335 "I have always wished for my computer to be as easy to use as my telephone; my wish has come true because I can no longer figure out how to use my telephone." -- Bjarne Stroustrup _________________________________________________ Philippine Linux Users' Group (PLUG) Mailing List [email protected] (#PLUG @ irc.free.net.ph) Read the Guidelines: http://linux.org.ph/lists Searchable Archives: http://archives.free.net.ph
