Hi all,
As you can see here
we encounter big problems with graphs, after performing some tunning on the database we increase the speed of the web interface by 200% as you can see on this screenshot:
And here you have the my.cnf setup:
key_buffer = 1500M
max_allowed_packet = 16M
thread_stack = 128K
thread_cache_size = 8
max_connections = 100
table_cache = 1800
thread_concurrency = 10
#
# * Query Cache Configuration
#
query_cache_limit = 100M
query_cache_size = 99M
So, now, we have a very very fast interface and everything seems to be going very very well, but there are a few very annoying things on database. With the issue of the database we installed on server a few tools for monitoring the database, mytop, mysqlreports and phpmyadmin. Here you have what phpmyadmin shows:
This MySQL server has been running for 4 days, 22 hours, 31 minutes and 12 seconds. It started up on Sep 11, 2008 at 09:54 AM.
Traffic______per hour
Received 40 GiB______344 MiB
Sent 61 GiB______523 MiB
Total 100 GiB______867 MiB
Connections__per hour_____%
max. concurrent connections 54________---_________---
Failed attempts 7,056______59.53______6.65%
Aborted 42_______0.00 k______0.04%
Total 106 k_____895.56_____100.00%
Slow_queries 3,982
Innodb_buffer_pool_pages_dirty 8,727
Innodb_buffer_pool_reads 732 k
Innodb_row_lock_waits 176
Handler_read_rnd 91 M
Handler_read_rnd_next 1,667 M
Created_tmp_disk_tables 66 M
Key_reads 8,020 k
Opened_tables 233
Those are the values showing as a problem, and also, using mytop the output shows that the key efficiency is just 22%. The biggest problem that i think we have is the "Handler_read_rnd_next" value and the "Innodb_buffer_pool_pages_dirty".
So, my question, as i don't have any idea regarding database tunning, with this outputs, do you think that the tunning we perform is ok or we will encounter database problems in the future?
I know that could be hard for reply to this question, so, thanks in advance for reading this
As you can see here
we encounter big problems with graphs, after performing some tunning on the database we increase the speed of the web interface by 200% as you can see on this screenshot:
And here you have the my.cnf setup:
key_buffer = 1500M
max_allowed_packet = 16M
thread_stack = 128K
thread_cache_size = 8
max_connections = 100
table_cache = 1800
thread_concurrency = 10
#
# * Query Cache Configuration
#
query_cache_limit = 100M
query_cache_size = 99M
So, now, we have a very very fast interface and everything seems to be going very very well, but there are a few very annoying things on database. With the issue of the database we installed on server a few tools for monitoring the database, mytop, mysqlreports and phpmyadmin. Here you have what phpmyadmin shows:
This MySQL server has been running for 4 days, 22 hours, 31 minutes and 12 seconds. It started up on Sep 11, 2008 at 09:54 AM.
Traffic______per hour
Received 40 GiB______344 MiB
Sent 61 GiB______523 MiB
Total 100 GiB______867 MiB
Connections__per hour_____%
max. concurrent connections 54________---_________---
Failed attempts 7,056______59.53______6.65%
Aborted 42_______0.00 k______0.04%
Total 106 k_____895.56_____100.00%
Slow_queries 3,982
Innodb_buffer_pool_pages_dirty 8,727
Innodb_buffer_pool_reads 732 k
Innodb_row_lock_waits 176
Handler_read_rnd 91 M
Handler_read_rnd_next 1,667 M
Created_tmp_disk_tables 66 M
Key_reads 8,020 k
Opened_tables 233
Those are the values showing as a problem, and also, using mytop the output shows that the key efficiency is just 22%. The biggest problem that i think we have is the "Handler_read_rnd_next" value and the "Innodb_buffer_pool_pages_dirty".
So, my question, as i don't have any idea regarding database tunning, with this outputs, do you think that the tunning we perform is ok or we will encounter database problems in the future?
I know that could be hard for reply to this question, so, thanks in advance for reading this