Saturation mémoire slow_query avec des ordres SQL "_transient_doing_cron"
... / Saturation mémoire slow_q...
BMPCreated with Sketch.BMPZIPCreated with Sketch.ZIPXLSCreated with Sketch.XLSTXTCreated with Sketch.TXTPPTCreated with Sketch.PPTPNGCreated with Sketch.PNGPDFCreated with Sketch.PDFJPGCreated with Sketch.JPGGIFCreated with Sketch.GIFDOCCreated with Sketch.DOC Error Created with Sketch.
Question

Saturation mémoire slow_query avec des ordres SQL "_transient_doing_cron"

by
EvelyneL2
Created on 2024-06-20 09:43:21 (edited on 2024-09-04 14:01:48) in Tâches automatiques (cron)

Bonjour,

Nous avons dans la slow-query.log des ordres SQL très longs et qui saturent la mémoire de notre webcloud database :

**(exemple de log )**
> INSERT INTO `wpstg7_options` (`option_name`, `option_value`, `autoload`) VALUES ('_transient_doing_cron', '1718867954.4777209758758544921875', 'yes') ON DUPLICATE KEY UPDATE `option_name` = VALUES(`option_name`), `option_value` = VALUES(`option_value`), `autoload` = VALUES(`autoload`);
> # Time: 2024-06-20T07:19:31.752449Z
> # User@Host: departement[departement] @ [10.27.21.130] Id: 15088
> # Query_time: 60.005867 Lock_time: 0.000005 Rows_sent: 0 Rows_examined: 0
> SET timestamp=1718867911;
> INSERT INTO `wpstg8_options` (`option_name`, `option_value`, `autoload`) VALUES ('_transient_doing_cron', '1718867911.7436010837554931640625', 'yes') ON DUPLICATE KEY UPDATE `option_name` = VALUES(`option_name`), `option_value` = VALUES(`option_value`), `autoload` = VALUES(`autoload`);
> # Time: 2024-06-20T07:19:31.756751Z
> # User@Host: departement[departement] @ [10.27.20.164] Id: 14987
> # _Query_time: 390.373829_ Lock_time: 0.000007 Rows_sent: 0 Rows_examined: 0
> SET timestamp=1718867581;
> INSERT INTO `wpstg7_options` (`option_name`, `option_value`, `autoload`) VALUES ('_transient_doing_cron', '1718867581.3809709548950195312500', 'yes') ON DUPLICATE KEY UPDATE `option_name` = VALUES(`option_name`), `option_value` = VALUES(`option_value`), `autoload` = VALUES(`autoload`);
> # Time: 2024-06-20T07:19:31.763391Z
> # User@Host: departement[departement] @ [10.27.20.164] Id: 14981

**_Question :_** que signifient ces ordres SQL et comment résoudre ces QUERY_TIME très longs (ex: Query_time: 390.373829) ?


Merci pour vos retours.


1 Reply ( Latest reply on 2024-07-30 07:31:00 by
^FabL
)

Bonjour,

Si le dysfonctionnement est toujours d'actualité, je vous inviterai à ajouter des éléments, tests effectués depuis la création de votre post.

Dans le cas contraire, n'hésitez pas à partager la solution afin d'en faire profiter le plus grand nombre,

^FabL