Mysql part en vrille

lansing · 2013-10-11 13:44:07

Bonjour,

Je ne sais pas si c'est depuis le passage en 0.84.2 mais lorsque j'utilise la recherche globable par exemple, MySQL monte à 100% de CPU pendant le temps de la recherche (10-15sec).
Ma base GLPI est assez petite donc à mon sens cela devrait être immédiat.
Faut il changer le moteur de la BDD (actuellement en MyISAM) ?
Déjà fait

mysqlcheck -o --all-databases

/etc/mysql/my.cnf

#
# The MySQL database server configuration file.
#
# You can copy this to one of:
# - "/etc/mysql/my.cnf" to set global options,
# - "~/.my.cnf" to set user-specific options.
# 
# One can use all long options that the program supports.
# Run program with --help to get a list of available options and with
# --print-defaults to see which it would actually understand and use.
#
# For explanations see
# http://dev.mysql.com/doc/mysql/en/server-system-variables.html

# This will be passed to all mysql clients
# It has been reported that passwords should be enclosed with ticks/quotes
# escpecially if they contain "#" chars...
# Remember to edit /etc/mysql/debian.cnf when changing the socket location.
[client]
port        = 3306
socket        = /var/run/mysqld/mysqld.sock

# Here is entries for some specific programs
# The following values assume you have at least 32M ram

# This was formally known as [safe_mysqld]. Both versions are currently parsed.
[mysqld_safe]
socket        = /var/run/mysqld/mysqld.sock
nice        = 0

[mysqld]
#
# * Basic Settings
#
user        = mysql
pid-file    = /var/run/mysqld/mysqld.pid
socket        = /var/run/mysqld/mysqld.sock
port        = 3306
basedir        = /usr
datadir        = /var/lib/mysql
tmpdir        = /tmp
language    = /usr/share/mysql/english
skip-external-locking
#
# Instead of skip-networking the default is now to listen only on
# localhost which is more compatible and is not less secure.
# bind-address        = 127.0.0.1
#
# * Fine Tuning
#
key_buffer        = 128M
max_allowed_packet    = 16M
thread_stack        = 192K
thread_cache_size       = 8
# This replaces the startup script and checks MyISAM tables if needed
# the first time they are touched
myisam-recover         = BACKUP
#max_connections        = 100
table_cache            = 128
#thread_concurrency     = 10
#
# * Query Cache Configuration
#
query_cache_limit    = 2M
query_cache_size        = 16M
#
# * Logging and Replication
#
# Both location gets rotated by the cronjob.
# Be aware that this log type is a performance killer.
# As of 5.1 you can enable the log at runtime!
#general_log_file        = /var/log/mysql/mysql.log
#general_log             = 1
#
# Error logging goes to syslog due to /etc/mysql/conf.d/mysqld_safe_syslog.cnf.
#
# Here you can see queries with especially long duration
#log_slow_queries    = /var/log/mysql/mysql-slow.log
#long_query_time = 2
#log-queries-not-using-indexes
#
# The following can be used as easy to replay backup logs or for replication.
# note: if you are setting up a replication slave, see README.Debian about
#       other settings you may need to change.
#server-id        = 1
#log_bin            = /var/log/mysql/mysql-bin.log
expire_logs_days    = 10
max_binlog_size         = 100M
#binlog_do_db        = include_database_name
#binlog_ignore_db    = include_database_name
#
# * InnoDB
#
# InnoDB is enabled by default with a 10MB datafile in /var/lib/mysql/.
# Read the manual for more InnoDB related options. There are many!
#
# * Security Features
#
# Read the manual, too, if you want chroot!
# chroot = /var/lib/mysql/
#
# For generating SSL certificates I recommend the OpenSSL GUI "tinyca".
#
# ssl-ca=/etc/mysql/cacert.pem
# ssl-cert=/etc/mysql/server-cert.pem
# ssl-key=/etc/mysql/server-key.pem



[mysqldump]
quick
quote-names
max_allowed_packet    = 16M

[mysql]
#no-auto-rehash    # faster start of mysql but no tab completition

[isamchk]
key_buffer        = 16M

#
# * IMPORTANT: Additional settings that can override those from this file!
#   The files must end with '.cnf', otherwise they'll be ignored.
#
!includedir /etc/mysql/conf.d/

//Bonus : comment faire pour cette recherche globale tape aussi dans les contacts/utilisateurs/entitées ?

Last edited by lansing (2013-10-11 13:49:26)

JMD · 2013-10-11 20:12:02

Vous faites quoi comme recherche globale ?

Il nous faudrait des exemples précis et les résultats du mode debug et des logs...

lansing · 2013-10-14 13:32:17

Par exemple un utilisateur m'appelle, je tape dans recherche globale les 4 derniers chiffres de son TELEPHONE pour le retrouver et ça mouline 15-20sec.
Rien dans \var\www\glpi\files\_log
Niveau de journalisation : 5
Traceurs : Oui

anthara · 2013-10-14 17:00:51

Bonjour,
nous avons exactement les même symptômes en allant dans assistance->ticket.
Le CPU du serveur s'affole et les requêtes mettent 10s à 20s à sexécuté.

Testé sur 2 serveurs différents avec les mêmes symptomes :

1 windows : Apache 2.2.20 / PHP 5.3.6 / MySQL 5.5.15
1 linux : Apache 2.2.15 / PHP 5.3.3 / MySQL 5.5.33

J'ai eu d'autres retours de collègues. Avec une base mysql 5.3 pas de lenteurs

Rien dans les logs nagios.

EDIT: pas de problème en version 0.83.2, problème visible en version 0.84.2. Pas testé sur une autre version de GLPI

Last edited by anthara (2013-10-14 17:22:28)

lansing · 2013-10-16 13:51:06

MAJ de MySQL 5.1 vers 5.5 : aucun changement

MoYo · 2013-10-16 14:26:19

C'est quoi la recherche globale pour vous ?

lansing · 2013-10-16 15:22:05

La recherche en haut à droite (en dessous de "déconnexion")

MoYo · 2013-10-16 15:30:48

En mode debug pouvez vous nous donner les requetes qui mettent longtemps à répondre ?

lansing · 2013-10-16 16:52:25

Pour commencer, je pense qu'il faudrait mettre à jour
http://www.glpi-project.org/wiki/doku.p … nfig:debug
et préciser qu'il faut soit se connecter en tant que "glpi", soit faire

UPDATE glpi_users SET use_mode=2 WHERE name='NAME';

sur SON utilisateur

Sinon :

SELECT 'glpi' AS currentuser, `glpi_softwares`.`entities_id`, `glpi_softwares`.`is_recursive`, `glpi_softwares`.`name` AS ITEM_0, `glpi_softwares`.`id` AS ITEM_0_2, `glpi_entities`.`completename` AS ITEM_1, `glpi_manufacturers`.`name` AS ITEM_2, GROUP_CONCAT(DISTINCT CONCAT(`glpi_softwareversions`.`name`,'$$',`glpi_softwareversions`.`id`) SEPARATOR '$$$$') AS ITEM_3, GROUP_CONCAT(DISTINCT CONCAT(`glpi_operatingsystems_0a35c270152be19b5c8a485502badcd7`.`name`,'$$',`glpi_operatingsystems_0a35c270152be19b5c8a485502badcd7`.`id`) SEPARATOR '$$$$') AS ITEM_4, COUNT(DISTINCT `glpi_computers_softwareversions_13619fc769728e036df7bb10e2d9ddc3`.`id`) AS ITEM_5, FLOOR(SUM(`glpi_softwarelicenses_e780fc704aeff0f78f91dca1936f74db`.`number`) * COUNT(DISTINCT `glpi_softwarelicenses_e780fc704aeff0f78f91dca1936f74db`.`id`) / COUNT(`glpi_softwarelicenses_e780fc704aeff0f78f91dca1936f74db`.`id`)) AS ITEM_6, MIN(`glpi_softwarelicenses_e780fc704aeff0f78f91dca1936f74db`.`number`) AS ITEM_6_2, GROUP_CONCAT(DISTINCT CONCAT(`glpi_softwarelicenses_7f86c22b2932c5ea934d5b1afd806dc2`.`name`, ' - ', `glpi_softwarelicenses_7f86c22b2932c5ea934d5b1afd806dc2`.`serial`, '$$', `glpi_softwarelicenses_7f86c22b2932c5ea934d5b1afd806dc2`.`id`) SEPARATOR '$$$$') AS ITEM_7, `glpi_softwares`.`id` AS id 
FROM `glpi_softwares`
LEFT JOIN `glpi_entities` ON (`glpi_softwares`.`entities_id` = `glpi_entities`.`id` )
LEFT JOIN `glpi_manufacturers` ON (`glpi_softwares`.`manufacturers_id` = `glpi_manufacturers`.`id` ) 
LEFT JOIN `glpi_softwareversions` ON (`glpi_softwares`.`id` = `glpi_softwareversions`.`softwares_id` )
LEFT JOIN `glpi_operatingsystems` AS glpi_operatingsystems_0a35c270152be19b5c8a485502badcd7 ON (`glpi_softwareversions`.`operatingsystems_id` = `glpi_operatingsystems_0a35c270152be19b5c8a485502badcd7`.`id` ) 
LEFT JOIN `glpi_computers_softwareversions` AS glpi_computers_softwareversions_13619fc769728e036df7bb10e2d9ddc3 ON (`glpi_softwareversions`.`id` = `glpi_computers_softwareversions_13619fc769728e036df7bb10e2d9ddc3`.`softwareversions_id` AND `glpi_computers_softwareversions_13619fc769728e036df7bb10e2d9ddc3`.`is_deleted_computer` = '0' AND `glpi_computers_softwareversions_13619fc769728e036df7bb10e2d9ddc3`.`is_template_computer` = '0' AND ( `glpi_computers_softwareversions_13619fc769728e036df7bb10e2d9ddc3`.`entities_id` IN ('0', '46', '45', '47', '43', '16', '4', '8', '12', '15', '19', '21', '29', '31', '38', '40', '42') ) ) 
LEFT JOIN `glpi_softwarelicenses` AS glpi_softwarelicenses_e780fc704aeff0f78f91dca1936f74db ON (`glpi_softwares`.`id` = `glpi_softwarelicenses_e780fc704aeff0f78f91dca1936f74db`.`softwares_id` AND ( `glpi_softwarelicenses_e780fc704aeff0f78f91dca1936f74db`.`entities_id` IN ('0', '46', '45', '47', '43', '16', '4', '8', '12', '15', '19', '21', '29', '31', '38', '40', '42') ) AND (`glpi_softwarelicenses_e780fc704aeff0f78f91dca1936f74db`.`expire` IS NULL OR `glpi_softwarelicenses_e780fc704aeff0f78f91dca1936f74db`.`expire` > NOW()) ) 
LEFT JOIN `glpi_softwarelicenses` AS glpi_softwarelicenses_7f86c22b2932c5ea934d5b1afd806dc2 ON (`glpi_softwares`.`id` = `glpi_softwarelicenses_7f86c22b2932c5ea934d5b1afd806dc2`.`softwares_id` AND ( `glpi_softwarelicenses_7f86c22b2932c5ea934d5b1afd806dc2`.`entities_id` IN ('0', '46', '45', '47', '43', '16', '4', '8', '12', '15', '19', '21', '29', '31', '38', '40', '42') ) ) 
WHERE `glpi_softwares`.`is_deleted` = '0' AND `glpi_softwares`.`is_template` = '0' AND ( `glpi_softwares`.`entities_id` IN ('0', '46', '45', '47', '43', '16', '4', '8', '12', '15', '19', '21', '29', '31', '38', '40', '42') ) AND ( ( `glpi_softwares`.`name` LIKE '%07 10%' OR `glpi_entities`.`completename` LIKE '%07 10%' OR `glpi_manufacturers`.`name` LIKE '%07 10%' OR `glpi_softwareversions`.`name` LIKE '%07 10%' OR `glpi_operatingsystems_0a35c270152be19b5c8a485502badcd7`.`name` LIKE '%07 10%' OR `glpi_softwarelicenses_7f86c22b2932c5ea934d5b1afd806dc2`.`serial` LIKE '%07 10%' ) ) GROUP BY `glpi_softwares`.`id` 
ORDER BY ITEM_0 ASC

10sec

Last edited by lansing (2013-10-16 16:52:46)

MoYo · 2013-10-16 17:10:23

peut donc correspondre à ce bug :
https://forge.indepnet.net/issues/4602

Vous devez avoir une liste de logiciel très lente à l'affichage également ?

le correctif proposé est le suivant :
https://forge.indepnet.net/projects/glp … ions/22006

lansing · 2013-10-16 17:47:33

C'est carrément mieux, on passe de 10-15 secondes à "immédiat"

Résolu !

sinon, il est prévu que la "recherche globale" tape aussi dans entités/utilisateurs (ou via un plugin déjà existant que j'aurai raté) ?

Last edited by lansing (2013-10-16 17:50:17)

MoYo · 2013-10-16 17:53:15

merci du retour non ce n'est pas prévu pour le moment.

On pourrait imaginer rendre configurable les éléments utilisable dans la recherche globale.
ticket créé ici pour analyse : https://forge.indepnet.net/issues/4604

anthara · 2013-10-17 12:07:31

Nous avons le problème sur cette requête.
Elle n'a rien a voir avec la recherche global. Cela se produit lorsque l'on va dans assistance->ticket.

SELECT 'glpi' AS currentuser, `glpi_tickets`.`id` AS ITEM_0, `glpi_tickets`.`name` AS ITEM_1, `glpi_tickets`.`id` AS ITEM_1_2, `glpi_tickets`.`content` AS ITEM_1_3, `glpi_tickets`.`status` AS ITEM_1_4, `glpi_entities`.`completename` AS ITEM_2, `glpi_tickets`.`status` AS ITEM_3, `glpi_tickets`.`date_mod` AS ITEM_4, `glpi_tickets`.`date` AS ITEM_5, `glpi_tickets`.`solvedate` AS ITEM_6, `glpi_tickets`.`priority` AS ITEM_7, GROUP_CONCAT(DISTINCT `glpi_users_647c2805c3795643b0f52f520e7cdb86`.`id` SEPARATOR '$$$$') AS ITEM_8, GROUP_CONCAT(DISTINCT CONCAT(`glpi_tickets_users_a900a61824c3906cc82f90407e525192`.`users_id`, ' ', `glpi_tickets_users_a900a61824c3906cc82f90407e525192`.`alternative_email`) SEPARATOR '$$$$') AS ITEM_8_2, GROUP_CONCAT(DISTINCT `glpi_users_c5e682856a6d6fe48b5aed8f8b238708`.`id` SEPARATOR '$$$$') AS ITEM_9, GROUP_CONCAT(DISTINCT CONCAT(`glpi_tickets_users_74690f2626744a37ace4c70dd87cea83`.`users_id`, ' ', `glpi_tickets_users_74690f2626744a37ace4c70dd87cea83`.`alternative_email`) SEPARATOR '$$$$') AS ITEM_9_2, `glpi_itilcategories`.`completename` AS ITEM_10, `glpi_tickets`.`due_date` AS ITEM_11, `glpi_tickets`.`status` AS ITEM_11_2, GROUP_CONCAT(DISTINCT CONCAT(`glpi_tickets_c8682549752288b41bb384bcbe018c97`.`name`,'$$', `glpi_tickets_c8682549752288b41bb384bcbe018c97`.`id`) SEPARATOR '$$$$') AS ITEM_12, COUNT(DISTINCT `glpi_ticketfollowups`.`id`) AS ITEM_13, COUNT(DISTINCT `glpi_tickettasks`.`id`) AS ITEM_14, GROUP_CONCAT(DISTINCT CONCAT(`glpi_groups_77277850fac99c62dbc26a804f22f50c`.`completename`,'$$',`glpi_groups_77277850fac99c62dbc26a804f22f50c`.`id`) SEPARATOR '$$$$') AS ITEM_15, `glpi_tickets`.`type` AS ITEM_16, `glpi_tickets`.`id` AS id 
FROM `glpi_tickets`
LEFT JOIN `glpi_entities` ON (`glpi_tickets`.`entities_id` = `glpi_entities`.`id` ) 
LEFT JOIN `glpi_tickets_users` AS glpi_tickets_users_a900a61824c3906cc82f90407e525192 ON (`glpi_tickets`.`id` = `glpi_tickets_users_a900a61824c3906cc82f90407e525192`.`tickets_id` AND `glpi_tickets_users_a900a61824c3906cc82f90407e525192`.`type` = 1 )
LEFT JOIN `glpi_users` AS glpi_users_647c2805c3795643b0f52f520e7cdb86 ON (`glpi_tickets_users_a900a61824c3906cc82f90407e525192`.`users_id` = `glpi_users_647c2805c3795643b0f52f520e7cdb86`.`id` ) 
LEFT JOIN `glpi_tickets_users` AS glpi_tickets_users_74690f2626744a37ace4c70dd87cea83 ON (`glpi_tickets`.`id` = `glpi_tickets_users_74690f2626744a37ace4c70dd87cea83`.`tickets_id` AND `glpi_tickets_users_74690f2626744a37ace4c70dd87cea83`.`type` = 2 )
LEFT JOIN `glpi_users` AS glpi_users_c5e682856a6d6fe48b5aed8f8b238708 ON (`glpi_tickets_users_74690f2626744a37ace4c70dd87cea83`.`users_id` = `glpi_users_c5e682856a6d6fe48b5aed8f8b238708`.`id` )
LEFT JOIN `glpi_itilcategories` ON (`glpi_tickets`.`itilcategories_id` = `glpi_itilcategories`.`id` ) 
LEFT JOIN `glpi_tickets_tickets` ON ((`glpi_tickets`.`id` = `glpi_tickets_tickets`.`tickets_id_1` OR `glpi_tickets`.`id` = `glpi_tickets_tickets`.`tickets_id_2`) ) 
LEFT JOIN `glpi_tickets` AS glpi_tickets_c8682549752288b41bb384bcbe018c97 ON ((`glpi_tickets_c8682549752288b41bb384bcbe018c97`.`id` = `glpi_tickets_tickets`.`tickets_id_1` OR `glpi_tickets_c8682549752288b41bb384bcbe018c97`.`id` = `glpi_tickets_tickets`.`tickets_id_2`) AND `glpi_tickets_c8682549752288b41bb384bcbe018c97`.`id` <> `glpi_tickets`.`id` ) 
LEFT JOIN `glpi_ticketfollowups` ON (`glpi_tickets`.`id` = `glpi_ticketfollowups`.`tickets_id` ) 
LEFT JOIN `glpi_tickettasks` ON (`glpi_tickets`.`id` = `glpi_tickettasks`.`tickets_id` ) 
LEFT JOIN `glpi_groups_tickets` AS glpi_groups_tickets_8fe4b8216083df6473c0597972c40717 ON (`glpi_tickets`.`id` = `glpi_groups_tickets_8fe4b8216083df6473c0597972c40717`.`tickets_id` AND `glpi_groups_tickets_8fe4b8216083df6473c0597972c40717`.`type` = 1 )
LEFT JOIN `glpi_groups` AS glpi_groups_77277850fac99c62dbc26a804f22f50c ON (`glpi_groups_tickets_8fe4b8216083df6473c0597972c40717`.`groups_id` = `glpi_groups_77277850fac99c62dbc26a804f22f50c`.`id` ) 
WHERE `glpi_tickets`.`is_deleted` = '0' AND ( `glpi_tickets`.`entities_id` IN ('0', '8', '9', '10', '11', '12', '176', '64', '14', '15', '16', '17', '174', '13', '2', '3', '4', '5', '1', '7', '177', '220', '18', '19', '20', '21', '65', '66', '77', '87', '99', '107', '108', '109', '110', '111', '112', '113', '114', '115', '116', '117', '118', '119', '120', '121', '122', '123', '124', '125', '126', '127', '128', '129', '130', '131', '132', '133', '134', '135', '136', '137', '138', '139', '140', '141', '142', '143', '144', '145', '146', '147', '148', '149', '150', '151', '152', '153', '154', '155', '156', '157', '158', '159', '160', '161', '162', '163', '164', '165', '166', '167', '168', '169', '170', '171', '172', '173', '219', '239', '178', '179', '180', '221', '222', '182', '183', '181', '22', '23', '44', '223', '224', '67', '68', '69', '70', '71', '72', '73', '74', '75', '76', '78', '79', '80', '81', '82', '83', '84', '85', '86', '88', '89', '90', '91', '92', '93', '94', '95', '96', '97', '98', '100', '101', '102', '103', '104', '105', '106', '185', '184', '186', '187', '188', '189', '190', '191', '192', '193', '194', '195', '196', '197', '198', '199', '200', '201', '202', '203', '204', '205', '206', '207', '208', '209', '210', '211', '212', '213', '214', '215', '216', '217', '218', '225', '226', '227', '228', '229', '230', '231', '232', '233', '234', '235', '236', '237', '238', '25', '24', '26', '27', '28', '29', '30', '31', '32', '33', '34', '35', '36', '37', '38', '39', '40', '41', '43', '42', '45', '46', '47', '48', '49', '50', '51', '52', '53', '54', '55', '56', '57', '58', '59', '60', '61', '62', '63', '240') ) AND ( `glpi_tickets`.`status` IN ('1','2','3','4') ) GROUP BY `glpi_tickets`.`id` 
ORDER BY ITEM_4 DESC

MoYo · 2013-10-17 12:14:40

Si vous avez la possibilité essayez de réduire les colonnes affichées. Trop de colonnes génére une requete trop complexe à traiter.

anthara · 2013-10-17 12:37:39

merci pour la réponse, mais ce type d'affichage ne posait aucun soucis sur la version précédente.
De plus j'ai le problème avec mon compte utilisateur alors que j'ai l'affichage par défaut.

MoYo · 2013-10-17 13:23:29

je comprend bien mais je ne trouve pas dans votre requete un problème similaire aux problème résolu dans ce sujet.

MoYo · 2013-10-17 13:45:42

Il faudrait pouvoir comparer la même requete dans la version précédente en fait.

anthara · 2013-10-17 14:22:58

Voici la requête sur la version 0.83.2:

SELECT 'glpi' AS currentuser, `glpi_tickets`.`id` AS ITEM_0, `glpi_tickets`.`name` AS ITEM_1, `glpi_tickets`.`id` AS ITEM_1_2, `glpi_tickets`.`content` AS ITEM_1_3, `glpi_tickets`.`status` AS ITEM_1_4, `glpi_entities`.`completename` AS ITEM_2, `glpi_entities`.`id` AS ITEM_2_2, `glpi_tickets`.`status` AS ITEM_3, `glpi_tickets`.`date_mod` AS ITEM_4, `glpi_tickets`.`date` AS ITEM_5, `glpi_tickets`.`solvedate` AS ITEM_6, `glpi_tickets`.`priority` AS ITEM_7, GROUP_CONCAT(DISTINCT `glpi_users_a5e2026cbcb683e774f93a59e24a62a4`.`id` SEPARATOR '$$$$') AS ITEM_8, GROUP_CONCAT(DISTINCT CONCAT(`glpi_tickets_users_d1524bb2ea1d461ab90aed3b5f0e7e60`.`users_id`, ' ', `glpi_tickets_users_d1524bb2ea1d461ab90aed3b5f0e7e60`.`alternative_email`) SEPARATOR '$$$$') AS ITEM_8_2, GROUP_CONCAT(DISTINCT `glpi_users_f201be21cd638ee780d08cba4ceff0d4`.`id` SEPARATOR '$$$$') AS ITEM_9, GROUP_CONCAT(DISTINCT CONCAT(`glpi_tickets_users_819efb92c8b927b345e489211ec8e43b`.`users_id`, ' ', `glpi_tickets_users_819efb92c8b927b345e489211ec8e43b`.`alternative_email`) SEPARATOR '$$$$') AS ITEM_9_2, `glpi_itilcategories`.`completename` AS ITEM_10, `glpi_tickets`.`due_date` AS ITEM_11, `glpi_tickets`.`status` AS ITEM_11_2, GROUP_CONCAT(`glpi_tickets_tickets`.`tickets_id_1` SEPARATOR '$$$$') AS ITEM_12, GROUP_CONCAT(`glpi_tickets_tickets`.`tickets_id_2` SEPARATOR '$$$$') AS ITEM_12_2, COUNT(DISTINCT `glpi_ticketfollowups`.`id`) AS ITEM_13, COUNT(DISTINCT `glpi_tickettasks`.`id`) AS ITEM_14, GROUP_CONCAT(DISTINCT `glpi_groups_a0fdb25a4e0967f334115fb0dbcee9ce`.`completename` SEPARATOR '$$$$') AS ITEM_15, `glpi_tickets`.`type` AS ITEM_16, `glpi_tickets`.`id` AS id 
FROM `glpi_tickets`
LEFT JOIN `glpi_entities` ON (`glpi_tickets`.`entities_id` = `glpi_entities`.`id` ) 
LEFT JOIN `glpi_tickets_users` AS glpi_tickets_users_d1524bb2ea1d461ab90aed3b5f0e7e60 ON (`glpi_tickets`.`id` = `glpi_tickets_users_d1524bb2ea1d461ab90aed3b5f0e7e60`.`tickets_id` AND `glpi_tickets_users_d1524bb2ea1d461ab90aed3b5f0e7e60`.`type` = 1 )
LEFT JOIN `glpi_users` AS glpi_users_a5e2026cbcb683e774f93a59e24a62a4 ON (`glpi_tickets_users_d1524bb2ea1d461ab90aed3b5f0e7e60`.`users_id` = `glpi_users_a5e2026cbcb683e774f93a59e24a62a4`.`id` ) 
LEFT JOIN `glpi_tickets_users` AS glpi_tickets_users_819efb92c8b927b345e489211ec8e43b ON (`glpi_tickets`.`id` = `glpi_tickets_users_819efb92c8b927b345e489211ec8e43b`.`tickets_id` AND `glpi_tickets_users_819efb92c8b927b345e489211ec8e43b`.`type` = 2 )
LEFT JOIN `glpi_users` AS glpi_users_f201be21cd638ee780d08cba4ceff0d4 ON (`glpi_tickets_users_819efb92c8b927b345e489211ec8e43b`.`users_id` = `glpi_users_f201be21cd638ee780d08cba4ceff0d4`.`id` )
LEFT JOIN `glpi_itilcategories` ON (`glpi_tickets`.`itilcategories_id` = `glpi_itilcategories`.`id` ) 
LEFT JOIN `glpi_tickets_tickets` ON ((`glpi_tickets`.`id` = `glpi_tickets_tickets`.`tickets_id_1` OR `glpi_tickets`.`id` = `glpi_tickets_tickets`.`tickets_id_2`) ) 
LEFT JOIN `glpi_ticketfollowups` ON (`glpi_tickets`.`id` = `glpi_ticketfollowups`.`tickets_id` ) 
LEFT JOIN `glpi_tickettasks` ON (`glpi_tickets`.`id` = `glpi_tickettasks`.`tickets_id` ) 
LEFT JOIN `glpi_groups_tickets` AS glpi_groups_tickets_d1524bb2ea1d461ab90aed3b5f0e7e60 ON (`glpi_tickets`.`id` = `glpi_groups_tickets_d1524bb2ea1d461ab90aed3b5f0e7e60`.`tickets_id` AND `glpi_groups_tickets_d1524bb2ea1d461ab90aed3b5f0e7e60`.`type` = 1 )
LEFT JOIN `glpi_groups` AS glpi_groups_a0fdb25a4e0967f334115fb0dbcee9ce ON (`glpi_groups_tickets_d1524bb2ea1d461ab90aed3b5f0e7e60`.`groups_id` = `glpi_groups_a0fdb25a4e0967f334115fb0dbcee9ce`.`id` ) 
WHERE `glpi_tickets`.`is_deleted` = '0' AND ( `glpi_tickets`.`status` IN ('new','assign','plan','waiting') ) GROUP BY `glpi_tickets`.`id` 
ORDER BY ITEM_4 DESC

EDIT : 0,586s pour executer la page en version 0.83.2 et 17,54s en version 0.84.2

Last edited by anthara (2013-10-17 14:26:52)

MoYo · 2013-10-17 15:15:08

ok je pense donc voir le problème.
ticket créé : https://forge.indepnet.net/issues/4605

Je vous apporte une solution le plus rapidement possible.

je pense que si vous supprimer la colonne ticket liés vous résoudrez temporairement votre problème.

anthara · 2013-10-17 15:24:05

merci.
La solution temporaire fonctionne très bien.
En attente d'un correctif.

MoYo · 2013-10-23 08:20:40

fix proposes here : https://forge.indepnet.net/projects/glp … ions/22072

Forum GLPI-Project

Announcement

#1 2013-10-11 13:44:07

Mysql part en vrille

#2 2013-10-11 20:12:02

Re: Mysql part en vrille

#3 2013-10-14 13:32:17

Re: Mysql part en vrille

#4 2013-10-14 17:00:51

Re: Mysql part en vrille

#5 2013-10-16 13:51:06

Re: Mysql part en vrille

#6 2013-10-16 14:26:19

Re: Mysql part en vrille

#7 2013-10-16 15:22:05

Re: Mysql part en vrille

#8 2013-10-16 15:30:48

Re: Mysql part en vrille

#9 2013-10-16 16:52:25

Re: Mysql part en vrille

#10 2013-10-16 17:10:23

Re: Mysql part en vrille

#11 2013-10-16 17:47:33

Re: Mysql part en vrille

#12 2013-10-16 17:53:15

Re: Mysql part en vrille

#13 2013-10-17 12:07:31

Re: Mysql part en vrille

#14 2013-10-17 12:14:40

Re: Mysql part en vrille

#15 2013-10-17 12:37:39

Re: Mysql part en vrille

#16 2013-10-17 13:23:29

Re: Mysql part en vrille

#17 2013-10-17 13:45:42

Re: Mysql part en vrille

#18 2013-10-17 14:22:58

Re: Mysql part en vrille

#19 2013-10-17 15:15:08

Re: Mysql part en vrille

#20 2013-10-17 15:24:05

Re: Mysql part en vrille

#21 2013-10-23 08:20:40

Re: Mysql part en vrille

Board footer