I have just started playing with MySQL about a week ago. I have read as much as I can about optimizing the performance of MySQL and believe I have everything setup according to the documenation i've read and am very skilled at Linux.
When we attempt to link a table from MySQL, using the MyODBC drivers, and simply open the linked table in microsoft access it literally takes 4 or 5 minutes to get the data back from MySQL and then every time we try to scroll down it takes another 4 or 5 minutes to see the next bit of data. Also during all this mysqld is running at 99% processor utilization but I do not see any kind of unusual memory paging activity or extreme disc utilization. Also, this box does nothing else and has no other services running, well besides ssh. Granted the table we are viewing has in excess of 1,000,000 (one million) rows of data but I believe something must be misconfigured somewhere. MySQL v3.23.47 is running on a Linux RH 7.1 with the RH stock kernel 2.4.7-10-SMP The box is a dual PIII 1.1 ghz with 1 gig of ram with two ibm 10,000 U160 SCSI drives running in mirror. On a side note M$ SQL server 7 blows threw this same set of data in 3 seconds flat (linked table in access) and its running on a 500 mhz NT 4 machine with SCSI-2 drives and only 256 meg of ram. Has anyone experienced this problem before? Anyone running MySQL and viewing large amounts of data in access with no latency like i'm experiencing? Any tips that are not in tech notes? Tweaks for MyODBC? Any different settings for high end servers/datasets like this? Or is this another stupid MicroShaft problem with the ODBC sh*t? Jeremy McNamara --------------------------------------------------------------------- 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
