scalibility over time?

jaga · **scalibility over time? -** 29-04-2006, 04:51 PM

I'm already a dedicated kayako user, but I'm concerned with how the app will perform once the db grows. My current install has been up for 6 months and since that time has received 4000 tickets, and it is still extremely fast. We have also test migrated a cerberus install resulted in 177,000 tickets -- and that is a bit slow. I've optimized all tables, but is there anything else to do? Does kayako purge old tickets over time? How large have other peoples tables grown?

jaga · **bump -** 02-05-2006, 12:34 AM

C'mon...

How many tickets are in your supportsuite install?
Is it still fast?

Extra · 12:58 AM

Well ok I'll offer a little instght..

76716 most current ticket numbersequential 4 months.

Current Database size = 594.28 MB

65 staff 3 shifts

406 pages in chat history - 4060 chats

CPU Usage on a dual Xeon Linux = 6.57

Very fast page response...

jaga · 03-05-2006, 04:17 PM

thanks for the info. Do you still expect it to work as quickly in a year from now? When you have an additional 300,000 tickets?

Extra · 03-05-2006, 05:05 PM

Obviously cannot tell for sure.

but running at 6% CPU straight lined, I think we have room to grow.

:-)

jaga · 13-05-2006, 05:04 AM

extra,
Thanks for the info. Are you using mysql on apache on the same box or did you split them up? Was mysql tuned heavily?

shazzy · 17-05-2006, 03:45 PM

Quote:

Originally Posted by Extra

CPU Usage on a dual Xeon Linux = 6.57

If that is a Linux machine load as suggested then the machine is already been over-used.

6.57 != 6% ...

A load of over 1 on a single cpu machine is considered as "higher than you would like" utilisation.
You need to check the idle time to get a good indication of the load.

jaga · 17-05-2006, 05:05 PM

I had assumed he meant .06 load or 6% on windows. Now I wonder...

Thread Tools	Search this Thread
Show Printable Version Email this Page	Search this Thread: Advanced Search
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
A report of total Billing Time?	NC Software	SupportSuite, eSupport and LiveResponse	8	11-10-2007 12:08 PM
Forwarding with time worked, and billable time vs. time worked.	tompopovic	SupportSuite, eSupport and LiveResponse	2	02-08-2006 09:48 PM
Date & Time on ticket bug?	sentono	SupportSuite, eSupport and LiveResponse	5	08-05-2006 08:54 PM

jaga Offline Member Posts: 54 Join Date: Nov 2005	bump - 02-05-2006, 12:34 AM C'mon... How many tickets are in your supportsuite install? Is it still fast?

Extra Offline Member Posts: 30 Join Date: Oct 2005	02-05-2006, 01:05 AM Well ok I'll offer a little instght.. 76716 most current ticket numbersequential 4 months. Current Database size = 594.28 MB 65 staff 3 shifts 406 pages in chat history - 4060 chats CPU Usage on a dual Xeon Linux = 6.57 Very fast page response... Last edited by Extra; 03-05-2006 at 12:58 AM.

jaga Offline Member Posts: 54 Join Date: Nov 2005	03-05-2006, 04:17 PM thanks for the info. Do you still expect it to work as quickly in a year from now? When you have an additional 300,000 tickets?

Extra Offline Member Posts: 30 Join Date: Oct 2005	03-05-2006, 05:05 PM Obviously cannot tell for sure. but running at 6% CPU straight lined, I think we have room to grow. :-)

jaga Offline Member Posts: 54 Join Date: Nov 2005	13-05-2006, 05:04 AM extra, Thanks for the info. Are you using mysql on apache on the same box or did you split them up? Was mysql tuned heavily?

jaga Offline Member Posts: 54 Join Date: Nov 2005	17-05-2006, 05:05 PM I had assumed he meant .06 load or 6% on windows. Now I wonder...