Hallo,
bin neu hier und hab schon viele Interessante Berichte hier gefunden nun zur Frage, habe hier auf einem Hetzner EQ4 i7 920 8 GB Ram LAMP 1 oscommerce shop täglich 800 Besucher und ein Magento schwach besucht läuft.
Habe schon etwas optimiert jedoch hat jemand noch ein paar Tipps wie man das unter Mageto noch besser zu laufen bekommt anbei tuning Primer und top
also Server ist nicht überfordert.
bin neu hier und hab schon viele Interessante Berichte hier gefunden nun zur Frage, habe hier auf einem Hetzner EQ4 i7 920 8 GB Ram LAMP 1 oscommerce shop täglich 800 Besucher und ein Magento schwach besucht läuft.
Habe schon etwas optimiert jedoch hat jemand noch ein paar Tipps wie man das unter Mageto noch besser zu laufen bekommt anbei tuning Primer und top
also Server ist nicht überfordert.
Code:
top - 14:46:38 up 53 days, 4:27, 1 user, load average: 0.18, 0.16, 0.10
Tasks: 281 total, 1 running, 279 sleeping, 0 stopped, 1 zombie
Cpu(s): 0.5%us, 0.2%sy, 0.0%ni, 99.3%id, 0.0%wa, 0.0%hi, 0.0%si, 0.0%st
Mem: 8193844k total, 7522048k used, 671796k free, 266520k buffers
Swap: 4198968k total, 772k used, 4198196k free, 6295316k cached
Code:
-- MYSQL PERFORMANCE TUNING PRIMER --
- By: Matthew Montgomery -
MySQL Version 5.0.51a-24+lenny3 x86_64
Uptime = 53 days 4 hrs 17 min 24 sec
Avg. qps = 116
Total Questions = 535438252
Threads Connected = 11
Server has been running for over 48hrs.
It should be safe to follow these recommendations
To find out more information on how each of these
runtime variables effects performance visit:
http://dev.mysql.com/doc/refman/5.0/en/server-system-variables.html
Visit http://www.mysql.com/products/enterprise/advisors.html
for info about MySQL's Enterprise Monitoring and Advisory Service
SLOW QUERIES
The slow query log is NOT enabled.
Current long_query_time = 2 sec.
You have 556 out of 535438273 that take longer than 2 sec. to complete
Your long_query_time seems to be fine
BINARY UPDATE LOG
The binary update log is NOT enabled.
You will not be able to do point in time recovery
See http://dev.mysql.com/doc/refman/5.0/en/point-in-time-recovery.html
WORKER THREADS
Current thread_cache_size = 256
Current threads_cached = 58
Current threads_per_sec = 0
Historic threads_per_sec = 0
Your thread_cache_size is fine
MAX CONNECTIONS
Current max_connections = 100
Current threads_connected = 11
Historic max_used_connections = 69
The number of used connections is 69% of the configured maximum.
Your max_connections variable seems to be fine.
INNODB STATUS
Current InnoDB index space = 28 M
Current InnoDB data space = 27 M
Current InnoDB buffer pool free = 0 %
Current innodb_buffer_pool_size = 8 M
Depending on how much space your innodb indexes take up it may be safe
to increase this value to up to 2 / 3 of total system memory
MEMORY USAGE
Max Memory Ever Allocated : 2.33 G
Configured Max Per-thread Buffers : 2.55 G
Configured Max Global Buffers : 586 M
Configured Max Memory Limit : 3.12 G
Physical Memory : 7.81 G
Max memory limit seem to be within acceptable norms
KEY BUFFER
Current MyISAM index space = 20 M
Current key_buffer_size = 512 M
Key cache miss rate is 1 : 802444
Key buffer free ratio = 81 %
Your key_buffer_size seems to be too high.
Perhaps you can use these resources elsewhere
QUERY CACHE
Query cache is enabled
Current query_cache_size = 64 M
Current query_cache_used = 27 M
Current query_cache_limit = 1 M
Current Query cache Memory fill ratio = 43.17 %
Current query_cache_min_res_unit = 2 K
Query Cache is 21 % fragmented
Run "FLUSH QUERY CACHE" periodically to defragment the query cache memory
If you have many small queries lower 'query_cache_min_res_unit' to reduce fragme
ntation.
MySQL won't cache query results that are larger than query_cache_limit in size
SORT OPERATIONS
Current sort_buffer_size = 8 M
Current read_rnd_buffer_size = 7 M
Sort buffer seems to be fine
JOINS
Current join_buffer_size = 2.00 M
You have had 1929936 queries where a join could not use an index properly
You should enable "log-queries-not-using-indexes"
Then look for non indexed joins in the slow query log.
If you are unable to optimize your queries you may want to increase your
join_buffer_size to accommodate larger joins in one pass.
Note! This script will still suggest raising the join_buffer_size when
ANY joins not using indexes are found.
OPEN FILES LIMIT
Current open_files_limit = 2110 files
The open_files_limit should typically be set to at least 2x-3x
that of table_cache if you have heavy MyISAM usage.
Your open_files_limit value seems to be fine
TABLE CACHE
Current table_cache value = 1000 tables
You have a total of 1134 tables
You have 1000 open tables.
Current table_cache hit rate is 2%
, while 100% of your table cache is in use
You should probably increase your table_cache
TEMP TABLES
Current max_heap_table_size = 16 M
Current tmp_table_size = 32 M
Of 2073763 temp tables, 2% were created on disk
Effective in-memory tmp_table_size is limited to max_heap_table_size.
Created disk tmp tables ratio seems fine
TABLE SCANS
Current read_buffer_size = 7 M
Current table scan ratio = 2080 : 1
read_buffer_size seems to be fine
TABLE LOCKING
Current Lock Wait ratio = 1 : 4440
You may benefit from selective use of InnoDB.
If you have long running SELECT's against MyISAM tables and perform
frequent updates consider setting 'low_priority_updates=1'
If you have a high concurrency of inserts on Dynamic row-length tables
consider setting 'concurrent_insert=2'.
