Slow performance on the database

[did12345]

On OTRS 3.1.11 my users find that OTRS is very slow when they add a note to a ticket..

I did a benchmark on the system and here are the results:
Insert time : 4s
Update time: 7s
Select time: 7s --> should not take mothe than 6s on an average system
Delete time : 5s


Any ideas to improve theese timings?

I already added memory to the server (has actually 9GB) who's sole function is to host OTRS! ...

[jojo]

Disk Speed could be also a cause for this

[arvas]

OTRS has a neat tool inside, i believe its called Support Assesmement inside the admin. See if you have any reds or yellows there.
I do not think you should do the OTRS benchmark, there is a big message saying do not do it on live machines
You might want to try hardware benchmarking tools if the Support assessment shows all clear, to check your harddisk and rams just in case.

[did12345]

Disk Speed could be also a cause for this

i'm going for disk speed and access... It's quite strange though, i have 10K RPM disks on my IBM x346 server....
and in the support assesment: everything is green! ...

[CSL]

Check your database status: memory use, cache use, thread creation, cache sizes, etc. Check for swap use on the machine (any swap use is generally not good). Check database size - is it larger than 9GB? If so, your OS isn't going to be able to cache everything it will want to, and you'll probably be hitting disk access bottlenecks as the others have said when it has to unload and read new content into memory.

If you're using MySQL (? you haven't said) you can use a script such as mysqltuner to check these things for you and give recommendations:
https://github.com/rackerhacker/MySQLTuner-perl

[petiserk]

Hi did,

What is your architecture? Do you use Linux or Windows system? Where is your database on storage or local disk? What do you use, mysql or mssql?

Best Regards,
Peter

[did12345]

hi i'm on a windows 2008 with mysql, storage is in on local disks

[did12345]

Check your database status: memory use, cache use, thread creation, cache sizes, etc. Check for swap use on the machine (any swap use is generally not good). Check database size - is it larger than 9GB? If so, your OS isn't going to be able to cache everything it will want to, and you'll probably be hitting disk access bottlenecks as the others have said when it has to unload and read new content into memory.

If you're using MySQL (? you haven't said) you can use a script such as mysqltuner to check these things for you and give recommendations:
https://github.com/rackerhacker/MySQLTuner-perl

Thnak you for your answer, the script only works on linux environments, sadly i'm on windows..

I just noticed in the logs, there is a persistant error as well:

[kernel:system:PID:PIDGET] unknown column 'process_change' in 'field list', SQL: 'SELECT Process_name, Process_id, Process_host, Process_create, Process_change'. rocess could not be found in the process table!


does anyone know how to stop this?

[crythias]

rename the column without capital P.

[spall]

Hi everyone,

There is a windows mysqltuner here

http://mysqltuner.codeplex.com/


hope this helps, I am about to try it myself.


Simon