On Saturday 21 December 2002 00:06, Steven Roussey wrote: > I wanted to thank the MySQL team for making such a great product! We > moved from 3.23 to 4.0.x a couple of months ago and everything works > great. Just upgraded to 4.0.6 and glad to see it work out of the box > without a rev 4.0.6a. Those glib issues were such a pain! > > 4.0.5a and 4.0.6 have been as solid as any 3.23.x in our experience. > > Just a note to users of Full Text Search: put it on some other machine. > FTS was basically clearing the MySQL and Linux caches with all its read > data. Putting it on a separate machine let all the other stuff run just > fine. > > Short example: > Main server: 3000 q/s Disk read: 540 KB/s Load: 1 > FTS server: 2 q/s Disk read: 7600 KB/s Load: 12 > > Our queries are not representative of anyone else's! YMMV! Just a note > on how FTS can really read a lot of data and how moving it can really > clear things up. Which brings me to: > > EXPLAIN feature request: to have EXPLAIN RESOURCES SELECT or something > similar to be able to show resource usage instead of query/index plan. > Resources like CPU, disk read, and disk write. Likely it should not > actually be EXPLAIN, since it would do the operation (where explain does > not). So maybe SELECT [CALC_RESOURCES] ... followed by a SHOW > RESOURCES_USAGE or something.
I've consulted about your question with Sinisa Milivojevic. Here is what he said: EXPLAIN can not do that, because explain does not know: * how much code will be traversed * how fragmented are tables * how many functions will have to be evaluated * how loaded is a system (is relevant on some OS's) * how big temp tables or temp files will be * how well ANALYZE'd are indices * etc -- For technical support contracts, goto https://order.mysql.com/?ref=ensita This email is sponsored by Ensita.net http://www.ensita.net/ __ ___ ___ ____ __ / |/ /_ __/ __/ __ \/ / Victoria Reznichenko / /|_/ / // /\ \/ /_/ / /__ [EMAIL PROTECTED] /_/ /_/\_, /___/\___\_\___/ MySQL AB / Ensita.net <___/ www.mysql.com --------------------------------------------------------------------- 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
