I am very disappointed at KVS. There is a hard limit on how big your website can get because KVS is not designed for handling large traffic. I see hundreds of non-essential features in KVS being developed or upgrade (which is great) but this issue should be priority number 1 and it looks like it doesnt look emergency to you, because probably only less than 1% of your customers hit this limit. Mechbunny doesnt have 10% of KVS features but they have figured it out long time ago how to load balance everything.
We changed the table structure to InnoDB and moved the database to a dedicated server. We are seeing less than 20% cpu load with old average of about 3-4. We have about 2.5 million uniques per day and 450K videos.
for load balancing you could always setup an SQL cluster and I’m pretty sure you could easily setup a rule based load balancing using last digit of the video ID to determine which front end server handles the request to avoid duplicating your cache.
How much traffic are you pushing with how many videos ?
KVS 5.5.0 development
in Announcements
Posted
We changed the table structure to InnoDB and moved the database to a dedicated server. We are seeing less than 20% cpu load with old average of about 3-4. We have about 2.5 million uniques per day and 450K videos.
for load balancing you could always setup an SQL cluster and I’m pretty sure you could easily setup a rule based load balancing using last digit of the video ID to determine which front end server handles the request to avoid duplicating your cache.
How much traffic are you pushing with how many videos ?