OTRS Performance Degraded

[flippertom]

Sometimes login to OTRS is very slow.
Once logged in, viewing tickets works at normal speed.
However, opening new phone ticket page and saving the ticket takes long time.(upto 2-5 minutes at times).
This effect lasts for about 10 mins after which everything works at normal speed.

There are not jobs running at such times and database queries are executed at normal speed.
What could be the cause of this degraded performance?

[crythias]

email not being able to send notifications.

[jojo]

rebuild of caches (and slow cache backend)

[flippertom]

But would emails cause the login to be slow?
Or does it cause the whole system to be slow in general.

And how to tackle both these cases...emails and slow cache...?

[crythias]

Login? You said after login.
Specifically after saving ticket. Check the logs.

[flippertom]

When I noticed the slow performance, I logged out and when I logged in again, even the log in took long time.
Will check the log next time the issue is reported after saving a ticket.

[crythias]

If the login is taking a long time, then check how authentication is provisioned. If it's built-in versus external (like ldap/Active Directory) the built-in authentication appears to be problems with the database structure (could be, or just bad hardware). Check for the usual suspects: table crashes, filesystem issues, RAM and CPU utilization, etc.

External authentication or demographics may be a network connectivity issue, especially if at least one of the sources is unreachable.