I'm interested in hearing from anyone using Kayako in a high ticket load environment.

We're fast approaching 100,000 tickets and the performance of Kayako is starting to become concerning, to the extent that we're thinking about setting Kayako up on it's own server. We have 5-10 people online in Kayako at any one time, and if we're all going between tickets and live chat, it takes too long.

Does anyone have experience of a high load Kayako and the performance you see as it grows? I'd be interested in hearing what, if anything, you have done to tweak the performance.

Hi Matt,
I think Kayako is solid for that many tickets, the problem that we see though is on tables like swparserlogdata and swparserlogs can fill up very fast if you have an active desk and an email address that has been posted on the site and harvested by some spiders..

-Steven

After emptying the tables Steven suggested, I suggest you also optimize your Kayako database from Admin CP > Database. It should speed up your application