Bug #8000 | Threads_connected very high value with hyperthreading technology | ||
---|---|---|---|
Submitted: | 19 Jan 2005 2:25 | Modified: | 30 Jun 2005 16:03 |
Reporter: | Ricardo Creasy | Email Updates: | |
Status: | No Feedback | Impact on me: | |
Category: | MySQL Server | Severity: | S2 (Serious) |
Version: | 4.1.9 | OS: | Linux (Fedora Core 2) |
Assigned to: | Assigned Account | CPU Architecture: | Any |
[19 Jan 2005 2:25]
Ricardo Creasy
[20 Jan 2005 16:34]
Ricardo Creasy
Display of the command SHOW PROCESSLIST on testing replicating the problem with 8 pc's with ODBC
Attachment: show_processlist.zip (application/x-zip-compressed, text), 44.44 KiB.
[21 Jan 2005 2:20]
Dean Ellis
I have tried as many variations/loads as I can think of and have so far not been able to repeat the problem. ie: threads_connected reports an accurate number, that being the number of threads that are in fact connected. Check SHOW PROCESSLIST and see if you do happen to have a large number of connections held open and idling. Otherwise, we will need a specific set of steps by which we can reproduce this behavior.
[23 Jan 2005 1:20]
Ricardo Creasy
Please notice that I have added a file with show processlist, is a zip,
[23 Jan 2005 1:23]
Ricardo Creasy
The name of the file added to the file on january 20, is show_processlist.zip and it contains an example of the result of show processlist, Try to send a select query and a couple of insert to differents tables, keep doing this for two to five minutes and you would notice the number of threads connected raising, Are you testing on a server with hyperthreading techonology? and FC2 installed?
[31 May 2005 14:14]
Jorge del Conde
I was unable to reproduce this behaviour using Hyperthreading & Win32
[31 May 2005 16:03]
Jorge del Conde
Ricardo, Can you please check that you don't have any DNS problems in your system ?
[1 Jul 2005 23: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".