slow connection from localhost
am 08.06.2009 18:42:49 von Jancsok Akos--3446237442-1804289383-1244479369=:37131
Content-Type: MULTIPART/alternative; BOUNDARY="3446237442-846930886-1244479369=:37131"
--3446237442-846930886-1244479369=:37131
Content-Type: TEXT/plain; CHARSET=ISO-8859-2
Content-Transfer-Encoding: QUOTED-PRINTABLE
hi,
I need some urgent help. We have encountered a problem, when we try to conn=
ect in shell with a mysql client to the mysqld (via socket or via localhost=
). The connection takes 5 to 50 seconds, or it happens that the connection =
is fast, but then the "use somethingdb;" needs 5 to 50 seconds.
We have tried to use some advice from here already: http://www.debianhelp=
..co.uk/mysqlperformance.htm We tried to use mysqltuner.pl, which is an opti=
mizing tool. Here we set "Maximum possible memory usage:", in fact the real=
memory usage is few megas only. The other problem, which we found out in =
mysqlreport.txt, that if we set "Max used" to any number, sooner or later i=
t gets full and that is why the "Maximum possible memory usage:" is huge i=
n the mysqltuner.txt. okay, so I can attach the mysql config currently used=
and the mysqlreport.txt and mysqltuner.txt. The problem comes when the lo=
ad increases during the weekend. However, this load is still not huge, arou=
nd 200 connections at a time. Hope someone can help us with some good advi=
ce. Thank you in advance, Viktor=20
______________________________________________________ __
Dr. Csern=
us Imre: A f=E9rfi - Rendelje meg 20% kedvezm=E9nnyel!
http://bookline.h=
u/product/home!execute.action?tabname=3Dkonyv&type=3D22&_v=3 DDr_Csernus_Imr=
e_A_ferfi&id=3D80504&tabname=3Dbook&affiliate=3Dfrejkakar877 9
--3446237442-846930886-1244479369=:37131
Content-Type: TEXT/html; CHARSET=ISO-8859-2
Content-Transfer-Encoding: QUOTED-PRINTABLE
hi,
I need some urgent help. We have encountered a problem, when=
we try to connect in shell with a mysql client to the mysqld (via socket o=
r via localhost). The connection takes 5 to 50 seconds, or it happens that =
the connection is fast, but then the "use somethingdb;" needs 5 t=
o 50 seconds.
We have tried to use some advice from here already: k" href=3D"http://www.debianhelp.co.uk/mysqlperformance.htm">http://www.deb=
ianhelp.co.uk/mysqlperformance.htm
We tried to use mysqltuner.pl, which is an optimizing tool. Here we set=0A&=
quot;Maximum possible memory usage:", in fact the real memory usage is=
few megas only. The other problem, which we found out in mysqlreport.=
txt, that if we set=0A"Max used" to any number, sooner or later i=
t gets full and that is why =0Athe "Maximum possible memory usage:&quo=
t; is huge in the mysqltuner.txt.
okay, so I can attach the mysql config currently used and the mysqlreport.t=
xt=0Aand mysqltuner.txt. The problem comes when the load increases dur=
ing the weekend. However, this=0Aload is still not huge, around 200 connect=
ions at a time. Hope someone can help us with some good advice. Thank =
you in advance, Viktor=0D
=0A
______________________=
__________________________________
/home!execute.action?tabname=3Dkonyv&type=3D22&_v=3DDr_Csern us_Imre_A_ferfi=
&id=3D80504&tabname=3Dbook&affiliate=3Dfrejkakar8779" "target=3D_blank">
Dr. Csernus Imre: A f=E9rfi - Rendelje meg 20% kedvezm=E9nnyel!
--3446237442-846930886-1244479369=:37131--
--3446237442-1804289383-1244479369=:37131
Content-Type: TEXT/plain; name=mysqlreport.txt; CHARSET=ISO-8859-2
Content-Disposition: attachment; filename=mysqlreport.txt
root@sun:~# mysqlreport
MySQL 5.0.32-Debian_7et uptime 0 1:2:8 Sun Jun 7 20:10:51 2009
__ Key ____________________________________________________________ _____
Buffer used 5.86M of 512.00M %Used: 1.14
Current 99.22M %Usage: 19.38
Write ratio 0.45
Read ratio 0.00
__ Questions ___________________________________________________________
Total 230.79k 61.91/s
Slow 723 0.19/s %Total: 0.31 %DMS: 2.39
DMS 30.20k 8.10/s 13.09
__ Table Locks _________________________________________________________
Waited 9.18k 2.46/s %Total: 30.23
Immediate 21.18k 5.68/s
__ Tables ____________________________________________________________ __
Open 577 of 1024 %Cache: 56.35
Opened 695 0.19/s
__ Connections _________________________________________________________
Max used 1227 of 2400 %Max: 51.12
Total 41.03k 11.01/s
__ Created Temp ________________________________________________________
Disk table 0 0.00/s
Table 56 0.02/s
File 0 0.00/s
--3446237442-1804289383-1244479369=:37131
Content-Type: TEXT/plain; name=mysqltuner.txt; CHARSET=ISO-8859-2
Content-Disposition: attachment; filename=mysqltuner.txt
root@sun:~# ./mysqltuner.pl
>> MySQLTuner 1.0.0 - Major Hayden
>> Bug reports, feature requests, and downloads at http://mysqltuner.com/
>> Run with '--help' for additional options and output filtering
-------- General Statistics --------------------------------------------------
[--] Skipped version check for MySQLTuner script
[OK] Currently running supported MySQL version 5.0.32-Debian_7etch10-log
[OK] Operating on 64-bit architecture
-------- Storage Engine Statistics -------------------------------------------
[--] Status: +Archive -BDB -Federated -InnoDB -ISAM -NDBCluster
[--] Data in MyISAM tables: 22M (Tables: 9)
[OK] Total fragmented tables: 0
-------- Performance Metrics -------------------------------------------------
[--] Up for: 1h 3m 4s (231K q [61.137 qps], 41K conn, TX: 184M, RX: 24M)
[--] Reads / Writes: 98% / 2%
[--] Total buffers: 602.0M global + 24.4M per thread (2400 max threads)
[!!] Maximum possible memory usage: 57.7G (367% of installed RAM)
[OK] Slow queries: 0% (733/231K)
[OK] Highest usage of available connections: 51% (1242/2400)
[OK] Key buffer size / total MyISAM indexes: 512.0M/8.6M
[OK] Key buffer hit rate: 99.7% (1M cached / 6K reads)
[OK] Query cache efficiency: 84.0% (159K cached / 189K selects)
[OK] Query cache prunes per day: 0
[OK] Temporary tables created on disk: 0% (0 on disk / 59 total)
[OK] Thread cache hit rate: 84% (6K created / 41K connections)
[OK] Table cache hit rate: 83% (577 open / 695 opened)
[OK] Open file limit used: 5% (605/12K)
[!!] Table locks acquired immediately: 70%
-------- Recommendations -----------------------------------------------------
General recommendations:
MySQL started within last 24 hours - recommendations may be inaccurate
Reduce your overall MySQL memory footprint for system stability
Enable the slow query log to troubleshoot bad queries
Optimize queries and/or use InnoDB to reduce lock wait
--3446237442-1804289383-1244479369=:37131
Content-Type: text/plain; charset=us-ascii
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/mysql?unsub=gcdmg-mysql-2@m.gmane.org
--3446237442-1804289383-1244479369=:37131--