Communauté Magento Francophone

J'ai suivi ce fil depuis le début, mais j'avoue ne pas avoir de réponse, désolé.

La réponse n'est pas évidente, mais j'ai de quoi solutionner ton problème je pense.

Tu peux réactiver tout tes caches sauf le LAYOUT_CACHE.

C'est celui là qui ralenti considérablement le traitement lors de toutes actions sur la commande.
Il y a quelques topic sur magentocommerce mais ils sont très bien caché et il n'y a pas de solution actuellement.

J'ai le même problème sur un site avec un volumétrie relativement importante.

Concernant ta double facturation, dans var/report tu dois avoir des report avec des "lock transaction timeout" ou encore des deadlocks. Là c'est plus un problème niveau Mysql.
Tu es sur une serveur dédié ou mutualisé ?

Bonjour,

Je teste cela et je vous mets au courant des résultats.

Je suis sur un dédié dual core, 4go de ram.

Y'a t il une config spéciale dans php.ini pour magento?

Oh oui, c'est un métier la configuration d'un serveur pour Magento.
Si c'est sur un dédié, je vous conseille déjà pour optimiser la base de donnée d'utiliser des script d'optimisation comme 'tuning primer' qui analyse l'état de votre serveur mysql et vous conseille sur les réglages à effectuer.

Voici le résultat du script 'tuning primer' que j'ai trouvé launchpad.net/mysql-tuning-primer

-- MYSQL PERFORMANCE TUNING PRIMER --
- By: Matthew Montgomery -

MySQL Version 5.1.55 x86_64

tuning-primer.sh: line 497: bc: command not found
tuning-primer.sh: line 498: bc: command not found
tuning-primer.sh: line 499: bc: command not found
tuning-primer.sh: line 500: bc: command not found
tuning-primer.sh: line 501: bc: command not found
tuning-primer.sh: line 502: bc: command not found
Uptime = days hrs min sec
Avg. qps = 23
Total Questions = 4496175
Threads Connected = 1

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:
dev.mysql.com/doc/refman/5.1/en/server-system-variables.html
Visit 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 = 10.000000 sec.
You have 15 out of 4496196 that take longer than 10.000000 sec. to complete
tuning-primer.sh: line 403: bc: command not found
tuning-primer.sh: line 606: [: -gt: unary operator expected
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.1/en/point-in-time-recovery.html

WORKER THREADS
Current thread_cache_size = 8
Current threads_cached = 6
Current threads_per_sec = 0
Historic threads_per_sec = 0
Your thread_cache_size is fine

MAX CONNECTIONS
Current max_connections = 500
Current threads_connected = 2
Historic max_used_connections = 36
The number of used connections is 7% of the configured maximum.
You are using less than 10% of your configured max_connections.
Lowering max_connections could help to avoid an over-allocation of memory
See "MEMORY USAGE" section to make sure you are not over-allocating

INNODB STATUS
tuning-primer.sh: line 440: bc: command not found
Current InnoDB index space = M
tuning-primer.sh: line 440: bc: command not found
Current InnoDB data space = M
Current InnoDB buffer pool free = 77 %
tuning-primer.sh: line 440: bc: command not found
Current innodb_buffer_pool_size = G
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
tuning-primer.sh: line 1321: bc: command not found
tuning-primer.sh: line 1322: bc: command not found
tuning-primer.sh: line 1346: bc: command not found
tuning-primer.sh: line 1349: bc: command not found
tuning-primer.sh: line 1350: bc: command not found
tuning-primer.sh: line 1352: bc: command not found
tuning-primer.sh: line 1354: [: -gt: unary operator expected
tuning-primer.sh: line 459: [: max_memoryHR: integer expression expected
tuning-primer.sh: line 465: [: max_memoryHR: integer expression expected
tuning-primer.sh: line 471: [: max_memoryHR: integer expression expected
tuning-primer.sh: line 478: export: `=max_memoryHR': not a valid identifier
Max Memory Ever Allocated : bytes
tuning-primer.sh: line 459: [: per_thread_buffersHR: integer expression expected
tuning-primer.sh: line 465: [: per_thread_buffersHR: integer expression expected
tuning-primer.sh: line 471: [: per_thread_buffersHR: integer expression expected
tuning-primer.sh: line 478: export: `=per_thread_buffersHR': not a valid identifier
Configured Max Per-thread Buffers : bytes
tuning-primer.sh: line 459: [: global_buffersHR: integer expression expected
tuning-primer.sh: line 465: [: global_buffersHR: integer expression expected
tuning-primer.sh: line 471: [: global_buffersHR: integer expression expected
tuning-primer.sh: line 478: export: `=global_buffersHR': not a valid identifier
Configured Max Global Buffers : bytes
tuning-primer.sh: line 459: [: total_memoryHR: integer expression expected
tuning-primer.sh: line 465: [: total_memoryHR: integer expression expected
tuning-primer.sh: line 471: [: total_memoryHR: integer expression expected
tuning-primer.sh: line 478: export: `=total_memoryHR': not a valid identifier
Configured Max Memory Limit : bytes
tuning-primer.sh: line 440: bc: command not found
Physical Memory : G
Max memory limit seem to be within acceptable norms

KEY BUFFER
tuning-primer.sh: line 754: bc: command not found
tuning-primer.sh: line 755: bc: command not found
tuning-primer.sh: line 440: bc: command not found
Current MyISAM index space = M
tuning-primer.sh: line 440: bc: command not found
Current key_buffer_size = M
Key cache miss rate is 1 : 1379
Key buffer free ratio = %
tuning-primer.sh: line 792: [: -le: unary operator expected
tuning-primer.sh: line 796: [: -le: unary operator expected
Your key_buffer_size seems to be fine

QUERY CACHE
Query cache is supported but not enabled
Perhaps you should set the query_cache_size

SORT OPERATIONS
tuning-primer.sh: line 440: bc: command not found
Current sort_buffer_size = M
tuning-primer.sh: line 440: bc: command not found
Current read_rnd_buffer_size = M
Sort buffer seems to be fine

JOINS
tuning-primer.sh: line 440: bc: command not found
Current join_buffer_size = M
You have had 78115 queries where a join could not use an index properly
join_buffer_size >= 4 M
This is not advised
You should enable "log-queries-not-using-indexes"
Then look for non indexed joins in the slow query log.

OPEN FILES LIMIT
Current open_files_limit = 2500 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_open_cache = 512 tables
Current table_definition_cache = 256 tables
You have a total of 692 tables
You have 512 open tables.
Current table_cache hit rate is 6%
, while 100% of your table cache is in use
You should probably increase your table_cache
You should probably increase your table_definition_cache value.

TEMP TABLES
tuning-primer.sh: line 440: bc: command not found
Current max_heap_table_size = M
tuning-primer.sh: line 440: bc: command not found
Current tmp_table_size = M
Of 781812 temp tables, 36% were created on disk
Effective in-memory tmp_table_size is limited to max_heap_table_size.
Perhaps you should increase your tmp_table_size and/or max_heap_table_size
to reduce the number of disk-based temporary tables
Note! BLOB and TEXT columns are not allow in memory tables.
If you are using these columns raising these values might not impact your
ratio of on disk temp tables.

TABLE SCANS
tuning-primer.sh: line 440: bc: command not found
Current read_buffer_size = M
Current table scan ratio = 56 : 1
read_buffer_size seems to be fine

TABLE LOCKING
Current Lock Wait ratio = 1 : 2501312
Your table locking seems to be fine

tu devrais installer bc, c'est étrange qu'il ne soit pas installé.
Et recharger le script et lui mettre les bon droits :

Voilà c'est fait. J'ai repris les meme couleurs que script affiche dans le shell.



-- MYSQL PERFORMANCE TUNING PRIMER --
- By: Matthew Montgomery -

MySQL Version 5.1.55 x86_64

Uptime = 2 days 5 hrs 11 min 37 sec
Avg. qps = 23
Total Questions = 4582480
Threads Connected = 1

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:
dev.mysql.com/doc/refman/5.1/en/server-system-variables.html
Visit 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 = 10.000000 sec.
You have 15 out of 4582501 that take longer than 10.000000 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 dev.mysql.com/doc/refman/5.1/en/point-in-time-recovery.html

WORKER THREADS
Current thread_cache_size = 8
Current threads_cached = 6
Current threads_per_sec = 0
Historic threads_per_sec = 0
Your thread_cache_size is fine

MAX CONNECTIONS
Current max_connections = 500
Current threads_connected = 2
Historic max_used_connections = 36
The number of used connections is 7% of the configured maximum.
You are using less than 10% of your configured max_connections.
Lowering max_connections could help to avoid an over-allocation of memory
See "MEMORY USAGE" section to make sure you are not over-allocating

INNODB STATUS
Current InnoDB index space = 259 M
Current InnoDB data space = 416 M
Current InnoDB buffer pool free = 77 %
Current innodb_buffer_pool_size = 2.92 G
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 : 4.18 G
Configured Max Per-thread Buffers : 16.72 G
Configured Max Global Buffers : 2.97 G
Configured Max Memory Limit : 19.70 G
Physical Memory : 3.83 G

nMax memory limit exceeds 90% of physical memory

KEY BUFFER
Current MyISAM index space = 53 M
Current key_buffer_size = 32 M
Key cache miss rate is 1 : 1376
Key buffer free ratio = 81 %
Your key_buffer_size seems to be fine

QUERY CACHE
Query cache is supported but not enabled
Perhaps you should set the query_cache_size

SORT OPERATIONS
Current sort_buffer_size = 8 M
Current read_rnd_buffer_size = 16 M
Sort buffer seems to be fine

JOINSe--
Current join_buffer_size = 8.00 M
You have had 78129 queries where a join could not use an index properly
join_buffer_size >= 4 M
This is not advised
You should enable "log-queries-not-using-indexes"
Then look for non indexed joins in the slow query log.

OPEN FILES LIMIT
Current open_files_limit = 2500 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_open_cache = 512 tables
Current table_definition_cache = 256 tables
You have a total of 692 tables
You have 512 open tables.
Current table_cache hit rate is 4%
, while 100% of your table cache is in use
You should probably increase your table_cache
You should probably increase your table_definition_cache value.

TEMP TABLES
Current max_heap_table_size = 32 M
Current tmp_table_size = 64 M
Of 800632 temp tables, 36% were created on disk
Effective in-memory tmp_table_size is limited to max_heap_table_size.
Perhaps you should increase your tmp_table_size and/or max_heap_table_size
to reduce the number of disk-based temporary tables
Note! BLOB and TEXT columns are not allow in memory tables.
If you are using these columns raising these values might not impact your
ratio of on disk temp tables.

TABLE SCANS
Current read_buffer_size = 2 M
Current table scan ratio = 56 : 1
read_buffer_size seems to be fine

TABLE LOCKING
Current Lock Wait ratio = 1 : 2552935
Your table locking seems to be fine

Tu as ta réponse avec tous les éléments en rouge
à toi d'ajuster les paramètres.

Comme tu peux le voir, tu as déjà un gros problème de mémoire !