Mailing List
Home
MySQL General - General MySQL discussion
MaxDB - Everything about MaxDB, formerly known as SAP DB
MySQL on Win32 - Runing MySQL on Windows 9x/Me/NT/2000/XP
MySQL++ - Programming with the C++ API to MySQL
ODBC - ODBC with the MySQL Connector/ODBC driver
Java Help - Mostly related to the MySQL Connector/J driver
Perl - Perl support for MySQL with DBI and DBD::mysql
GUI - MySQL GUI Tools
Announcement
Subjects
mysql openssl Question
mysql:it 's a db not a dbms how it 's possible?!
Does the binary log enabling affect the MySQL performances?
Strange behavior, Table Level Permission
FULLTEXT query format question
Preventing Duplicate Entries
Comparing and writing out BLOBS
Executing MySQL Commands From Within C Program
Can 't access mysql after kernel upgrade
Mysql 4 0 Oracle Stored Procedure Trigger Conversion
Downgrade Mysql from 4 to 3 23
MySQL Cluster Software
mysql test 4 1 fails with the gis test
ERROR 2002: Can 't connect to local MySQL server through socket
Getting Identity after INSERT
Update one field with more fields from another table
ERROR 1045: Access denied for user: 'root@localhost ' (Using
password: NO)
mysql have same function mthod as Oracle decode()
 
Search:  
Power your search with and, or, +, -, or "some phrase" operators.
Post-upgrade slowdown, part II

Post-upgrade slowdown, part II

2004-04-08       - By Mark Thomas

 Back
Reply:     1     2  

Hello, all.

About two weeks ago, I posted a message describing the outcome of our
upgrade from a late 7.3 to 7.5.0.8.  Following the upgrade, database
performance dropped to 10-50% of what we had previously achieved on the
same hardware and OS.  I modified the cache settings and tried the
COROUTINES, but was unable to resolve the problem.  I ran the analyzer and
checked the kernel logs, but the engine seems unaware that performance has
actually changed.

Last weekend, we rebuilt the instance from scratch as version 7.5.0.8, and
used ODBC and loadercli DATALOAD statements to repopulate the tables.  
Performance was fine--until yesterday.  The problem has suddenly
reappeared, and db performance is at a crawl.  In 2 years of using 7.3, we
never had a problem like this.

I have run out of ideas on how to fix this.  My superiors are pressuring me
to return us to 7.3.  Does anyone have any ideas whatsoever about what I
should do?

Platform: dual Pentium 3 running SuSE Linux 8.0.

--
Mark Thomas
United Drugs


--
MaxDB Discussion Mailing List
For list archives: http://lists.mysql.com/maxdb
To unsubscribe:    http://lists.mysql.com/maxdb?unsub=mysql@(protected)