You are not logged in.
- Topics: Active | Unanswered
Announcement
Download last stable version of GLPI - What can you do for GLPI ? : Contribute
Pages: 1
#1 2017-02-08 17:03:38
- KKAdmin
- Member
- From: Germany
- Registered: 2010-03-05
- Posts: 959
glpi mysql performance sometimes slow
Hi,
don't know very much about perfomance tuning about mysql.
Is the basic configuration of my system good for glpi ?
1000 devices
300 tickets per month
no fusion / no ocs
There are moments where glpi is slow. we are waiting for something. I think for db request.
best regards
armin
myuser@myhostname:~# cat /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
lc-messages-dir = /usr/share/mysql
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 = 0.0.0.0
#
# * Fine Tuning
#
key_buffer = 16M
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 = 64
#thread_concurrency = 10
#
# * Query Cache Configuration
#
query_cache_limit = 1M
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 log - should be very few entries.
#
log_error = /var/log/mysql/error.log
#
# 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/cpu
root@inventar01:~# cat /proc/cpuinfo
processor : 0
vendor_id : GenuineIntel
cpu family : 6
model : 37
model name : Intel(R) Xeon(R) CPU E5645 @ 2.40GHz
stepping : 1
microcode : 0x15
cpu MHz : 2400.085
cache size : 12288 KB
physical id : 0
siblings : 1
core id : 0
cpu cores : 1
apicid : 0
initial apicid : 0
fdiv_bug : no
f00f_bug : no
coma_bug : no
fpu : yes
fpu_exception : yes
cpuid level : 11
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts mmx fxsr sse sse2 ss nx rdtscp lm constant_tsc arch_perfmo n pebs bts xtopology tsc_reliable nonstop_tsc aperfmperf pni pclmulqdq ssse3 cx1 6 sse4_1 sse4_2 x2apic popcnt aes hypervisor lahf_lm arat epb dtherm
bogomips : 4800.17
clflush size : 64
cache_alignment : 64
address sizes : 40 bits physical, 48 bits virtual
power management:
processor : 1
vendor_id : GenuineIntel
cpu family : 6
model : 37
model name : Intel(R) Xeon(R) CPU E5645 @ 2.40GHz
stepping : 1
microcode : 0x15
cpu MHz : 2400.085
cache size : 12288 KB
physical id : 2
siblings : 1
core id : 0
cpu cores : 1
apicid : 2
initial apicid : 2
fdiv_bug : no
f00f_bug : no
coma_bug : no
fpu : yes
fpu_exception : yes
cpuid level : 11
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts mmx fxsr sse sse2 ss nx rdtscp lm constant_tsc arch_perfmo n pebs bts xtopology tsc_reliable nonstop_tsc aperfmperf pni pclmulqdq ssse3 cx1 6 sse4_1 sse4_2 x2apic popcnt aes hypervisor lahf_lm arat epb dtherm
bogomips : 4800.17
clflush size : 64
cache_alignment : 64
address sizes : 40 bits physical, 48 bits virtual
power management:ram
root@inventar01:~# free -m
Gesamt Belegt Frei Gemeinsam Puffer Cache
Speicher: 1001 629 372 65 59 377
-/+ Puffer/Cache: 192 809
Auslagerungsdatei: 883 0 883You can mark this threat as [resolved] in subject of your threat. (This is only available edit of the first post.) It is good for users who help others to quickly see which post is still open.
##############################################
GLPI 9.3.3
Offline
#2 2017-02-08 17:56:26
- eulogy
- Member
- Registered: 2013-10-11
- Posts: 118
Re: glpi mysql performance sometimes slow
Your "uptime" information?
Offline
#3 2017-02-08 18:09:03
- ddurieux
- Plugins Dev
- From: Propières, France
- Registered: 2005-06-17
- Posts: 7,521
Re: glpi mysql performance sometimes slow
Perhaps it's a problem with latence on send notifications mails (like you create new ticket...)
Offline
#4 2017-02-08 18:55:37
- KKAdmin
- Member
- From: Germany
- Registered: 2010-03-05
- Posts: 959
Re: glpi mysql performance sometimes slow
latence with notification: I have a cronjob for all glpi tasks.
uptime: I rebooted today. I did release update from 9.1.1. too 9.1.2
edit:
i send mails over mail queue (1 min delay setting)
Last edited by KKAdmin (2017-02-08 18:56:51)
You can mark this threat as [resolved] in subject of your threat. (This is only available edit of the first post.) It is good for users who help others to quickly see which post is still open.
##############################################
GLPI 9.3.3
Offline
#5 2017-02-08 19:21:08
- KKAdmin
- Member
- From: Germany
- Registered: 2010-03-05
- Posts: 959
Re: glpi mysql performance sometimes slow
Could i have other bad config ?
http://forum.glpi-project.org/viewtopic.php?id=156025
You can mark this threat as [resolved] in subject of your threat. (This is only available edit of the first post.) It is good for users who help others to quickly see which post is still open.
##############################################
GLPI 9.3.3
Offline
#6 2017-02-09 00:24:25
- ddurieux
- Plugins Dev
- From: Propières, France
- Registered: 2005-06-17
- Posts: 7,521
Re: glpi mysql performance sometimes slow
some notifications sent directly (so not use queue) for the moment like notifications in ticket creation
Offline
#7 2017-02-09 14:46:25
- eulogy
- Member
- Registered: 2013-10-11
- Posts: 118
Re: glpi mysql performance sometimes slow
I mean "uptime" for load average indicators, not for time is up and running.
"Maybe" your CPU load average is too high, and performance is slow, if that's the circunstance, then you should look at other services running in the server.
If your load average is over 2,00 then you have a situation to resolve in your server.
Also try checking hard disk performance, sometimes hard disks makes everything soooo freaking slow when they are about to die.
Last edited by eulogy (2017-02-09 14:50:39)
Offline
#8 2017-03-20 11:26:45
- KKAdmin
- Member
- From: Germany
- Registered: 2010-03-05
- Posts: 959
Re: glpi mysql performance sometimes slow
04:22:01 pgpgin/s pgpgout/s fault/s majflt/s pgfree/s pgscank/s pgscand/s pgsteal/s %vmeff
09:44:01 0,00 5,24 207,80 0,00 140,89 0,00 0,00 0,00 0,00
09:46:01 5,37 7,34 283,43 0,04 183,22 0,00 0,00 0,00 0,00
09:48:01 124,82 28,46 1274,03 0,94 641,70 0,00 0,00 0,00 0,00
09:50:01 0,23 19,99 321,80 0,03 196,59 0,00 0,00 0,00 0,00
09:52:01 1,53 19,06 572,61 0,03 341,78 0,00 0,00 0,00 0,00Okay and now 
?
You can mark this threat as [resolved] in subject of your threat. (This is only available edit of the first post.) It is good for users who help others to quickly see which post is still open.
##############################################
GLPI 9.3.3
Offline
Pages: 1