Submitting changes to tickets takes FOREVER

[tical]

I've optimized the database tables from the admin, but the app still appears to be running VERY slowly as of lately.

Especially when making batch changes to ticket status... it literally takes about 45 seconds to mark one ticket as closed.

Anyone here ever have a similar issue?

[AKL-MFCU]

not at all, thats very strange. Whats it looking like on the CPU usage on the mysql database when you run the change? If theres a huge amount of activity then there may be a bigger problem with the server, however if there is a very limited activity and it takes a long time, there are options in mysql that restrict usage on the processor, memory, etc. and can be your cause. We have a huge database of tickets (around 89,000 tickets right now many with attachments) and its still just as quick.

[tical]

I monitored it from the submitting of the close action all the way through... the load was at 0 the WHOLE way through.

It just takes so long to close anything

This is the server load about halfway through the ticket submission wait, it didn't jump at all.


top - 19:30:31 up 98 days, 19:58, 1 user, load average: 0.00, 0.00, 0.00
Tasks: 89 total, 1 running, 87 sleeping, 0 stopped, 1 zombie
Cpu(s): 0.0% us, 0.0% sy, 0.0% ni, 100.0% id, 0.0% wa, 0.0% hi, 0.0% si
Mem: 2074952k total, 1216436k used, 858516k free, 102112k buffers
Swap: 4096564k total, 0k used, 4096564k free, 903568k cached

[tical]

i cant take this anymore! someone help me

[flamecake]

Originally Posted by tical

i cant take this anymore! someone help me

Wich browser do you use?
We have some similar problems with Opera 9 here. IE or Firefox work well.

[tical]

I am using IE 6, this is becoming very annoying... it appears to not be server related but more client side.

If I hit submit and its lagging, i can just refresh the page or click the list of tickets and it appears as if everything has been processed fine.

but the app just takes forever to redirect..

[snook789]

Try FireFox

[keyguru]

I don't know if it helps or not but on our side Kayako became extremely slow when we switched to SMTP processing of our e-mails. We did it because no staff replies were sent to our clients, autorespondet worked, forward and cc worked but just clicking post reply did not deliver e-mails to our clients. As soon we switched to smtp e-mails are processed correctly. However Kayako became extremely slow processing notes and reply - 45-60 seconds at a time.