I have a table with 22,371,273 rows, current type is MyISAM. I have one
query tha took nearly 5 hours to complete. I do not know if this like
it should be or not, but I thought I'd ask the list. My gut feeling is
the `gropu by` that's slowing it down but nonetheless 5 hours seems
excessive. I'm trying to find the source of the limitation and work
from there.
Mysql:
4.0.18-standard, precompiled 32-bit sparc 2.8
Server:
Sun 420
Solaris 2.8
4x450MHZ Ultrasparc-II
4GB Ram
Two 50gb mounts, fiber channel scsi to EMC.
Brand new systems, totally idle.
I think everything relevant is here. The skinny: full table scan on
22 million rows, group and insert into new table. MyISAM and InnoDB
appear to give similar results when used as the destination
('new_table').
insert into new_table
select month_day, floor(bucket/3) as bucket, date, src, avg(value) as
value
from source_table
group by month_day, bucket, src;
Relevant `explain` details:
Full table scan: 22,371,273 rows, Using temporary; Using filesort
Query OK, 11495208 rows affected (4 hours 47 min 21.01 sec)
Records: 11495208 Duplicates: 0 Warnings: 0
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
