Aaron Williams wrote: > The tables run upwards of around 13-15 gigs each. The nature of the > data forces me to search the entire contents (looking for unique > values) around 3000 times a day. The server is running Solaris 2.8,
Do you have an index on the columns you are querying for unique values? That will help. If you do not need live and instant unique lists, you could (once every 30 minutes say) populate a special table with the unique values. With locking, etc. of course. > > with MySQL 3.9.43 compiled in 64bit mode. All tables are currently > MyISAM tables. (Will probably be going with InnoDB, but large file > support was -just- released). InnoDB might help because it does have row-level locking. > isn't disk bound. Running multiple intenses of the queries shows the > same results, 75% idle, meaning only one CPU is being used. AFAIK, 3.23.x only supports one CPU per thread/select. b. --------------------------------------------------------------------- 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
