Bug #17571 the perform efficiency of server descends gradually with long time running
Submitted: 20 Feb 2006 10:40 Modified: 20 Mar 2006 11:51
Reporter: ming lu Email Updates:
Status: No Feedback Impact on me:
None 
Category:MySQL Server Severity:S5 (Performance)
Version:5.0.18 OS:Linux (Redhat9)
Assigned to: CPU Architecture:Any

[20 Feb 2006 10:40] ming lu
Description:
    We do a performance test against to the mysql server 5.0.18(redhat9) with a program writed according to the TPC-C standard. But i find that the perform efficiency of server descends gradually with long time running. 
    The program simulated a application with 500 coinstantaneous connects. At the first, the perform efficiency is quit good, but the same transaction's response time become more longer with long time running.
    I do a same test against to the mysql server 5.0.18 in windows platform, it doesn't has this problem, it could works correct all along.

My test environment:
   Mysql Server: 5.0.18
   CPU: celeron 3.0 GHZ
   Memory: 2GB
   OS: Redhat9.0

How to repeat:
see the description
[20 Feb 2006 10:41] ming lu
the database setting

Attachment: my.cnf (application/octet-stream, text), 4.98 KiB.

[20 Feb 2006 11:51] Valeriy Kravchuk
Thank you for a problem report. Please, specify the exact MySQL package (RPM, tar.gz) you had used on Red Hat 9. Can you send my.ini and my.cnf files and SHOW GLOBAL STATUS results (after restart or FLUSH STATUS and running your test application) from both machines?
[28 Feb 2006 6:21] ming lu
my.cnf (linux)

Attachment: my.cnf (application/octet-stream, text), 5.05 KiB.

[28 Feb 2006 6:21] ming lu
my.ini (windows)

Attachment: my.ini (application/octet-stream, text), 9.41 KiB.

[28 Feb 2006 6:22] ming lu
show_global_status_Linux

Attachment: show_global_status_Linux.txt (text/plain), 11.61 KiB.

[28 Feb 2006 6:22] ming lu
show_global_status_windows

Attachment: show_global_status_windows.txt (text/plain), 12.57 KiB.

[21 Mar 2006 0:00] Bugs System
No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".