On Wed, Apr 10, 2002 at 08:39:03PM +0200, Benjamin Pflugmann wrote:
> 
> Hm. From vmstat output it looks like the second query is disk-bound on
> writing. Most probably writing temporary table(s) as EXPLAIN tells so
> (compare http://www.mysql.com/doc/E/X/EXPLAIN.html).

Agreed.

[snip]

> Well, to sum up: Your first query mainly seems to be bound on disk
> read speed (your table is about 1GB?). The second one needs a much
> larger tmp table (which it also has to sort!) and "trashes" your disk,
> that's probably why the machine feels unresponsive. 

That's what I'm thinking as well.

> For now, I have no further ideas than playing with "tmp_table_size"
> and trying to use an index over all column.

Please do post the results.  I'm very curious to see what helps.  I
don't expect an index to make any difference.  But ya never know.

> Anybody else?

Jeremy
-- 
Jeremy D. Zawodny, <[EMAIL PROTECTED]>
Technical Yahoo - Yahoo Finance
Desk: (408) 349-7878   Fax: (408) 349-5454   Cell: (408) 685-5936

MySQL 3.23.47-max: up 63 days, processed 1,719,432,003 queries (312/sec. avg)

---------------------------------------------------------------------
Before posting, please check:
   http://www.mysql.com/manual.php   (the manual)
   http://lists.mysql.com/           (the list archive)

To request this thread, e-mail <[EMAIL PROTECTED]>
To unsubscribe, e-mail <[EMAIL PROTECTED]>
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php

Reply via email to