high cpu usage after upgrade to v1.10.4

juanponz

Hello:I'm using osticket since 1.10.1, and i haven't had any problem.When I upgrade the version to 1.10.4 then, the usage of cpu is over the 90%, and the process that are eating the cpu is mysql.The server specifications are:- SO: Ubuntu 14.04.5- Apache 2.4.7- Mysql 5.5.59- PHP 5.5.9With the osticket 1.10.1, the cpu is above of 60%, while with the new version, the cpu is normally in 80-90%, the configuration of mysql is the next:port = 3306socket = /var/run/mysqld/mysqld.socksocket = /var/run/mysqld/mysqld.socknice = 0user = mysqlpid-file = /var/run/mysqld/mysqld.pidsocket = /var/run/mysqld/mysqld.sockport = 3306basedir = /usrdatadir = /var/lib/mysqltmpdir = /tmplc-messages-dir = /usr/share/mysqlskip-external-lockingkey_buffer = 16Mmax_allowed_packet = 16Mthread_stack = 192Kthread_cache_size = 8myisam-recover = BACKUPquery_cache_limit = 1Mquery_cache_size = 16Mlog_error = /var/log/mysql/error.logexpire_logs_days = 10max_binlog_size = 100Mquickquote-namesmax_allowed_packet = 16Mkey_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/anymore has the same problem???? How can I obtain better performance?Thanks and regards

ntozier

Granted I'm not on Linux for my OS, but my mySQL instance running three production osTicket sites, 6 wordpress sites, a Drupal site, and an intranet site sometimes breaks 6.8%, and is usually around 0.3%.I did some quick googling and was wondering what linux kernal you are running. I found this:Check for “leap second bug” – On July 1st 2015, a leap second was added to standard UTC time. In servers running old Linux kernel versions, and which uses time servers, this is seen to cause MySQL high load. If you have an old Linux kernel, try resetting the time using the command date -s “$(date)”.Here are two other things that I thought might assist you:Enable InnoDB to handle high number of concurrent connections – Check MySQL “PROCESSLIST”, and if you see a lot of queries in “LOCK” status, it means a lot queries are put on hold because MyISAM tables are handling other transactions. To fix this convert those tables into InnoDB engine which supports row-level locking.Enable persistent connections – If you have only a single application that receives thousands of connections per hour, enabling persistent MySQL connections can improve performance. If the server has multiple applications (like a shared web hosting server) this may not work.source: https://bobcares.com/blog/fix-mysql-high-cpu-usage/You might also find this article helpful.https://www.linode.com/docs/databases/mysql/how-to-optimize-mysql-performance-using-mysqltuner/

juanponz

Hi,thanks for the quickly response.I tryed the trick of "check for leap second bug", but in my server, this is not the problem.In all the articles, the reference to the bottleneck is caused by ram, but, in my problem, the problem is the high cpu usage.Today I had a mysql upgrade, and now, i'm in version 5.5.61In your server, how many cpu's has?I have 2 cpus assigneds (because osticket is an virtualized server) to the server, it's sufficient ??? .Now, I'm determining the number of connections when the CPU is in 100%, but, I have not more of 50/60 connectios.I noticed that, the cpu is growing up when the users use the advanced search, I know that this queries are some more complex, but in the previous version everything works perfectly.Thanks

juanponz

Hi,the last time that the cpu is 100%, the number of connections to myql are three.

sperrow

You should check which SQL query is is being executed when its taking up so much CPU, could be you are running into these issues:Could be related to you, if you got huge amount of attachments:https://github.com/osTicket/osTicket/issues/4309Few pull requests are outstanding, don't apply to live environment:https://github.com/osTicket/osTicket/pull/4441https://github.com/osTicket/osTicket/pull/4479 (exporting dataset, most likely not related)Based on the investigation if its one query or many, you could search osticket's github - maybe someone else also had the same issue.Thanks,

ntozier

juanponz, We run in a VM also. 1 socket, 2 cores (Cores are 2.663 Ghz) and 12 GB RAM.