I just wanted to get a feeler about database size. I've been using Eventum for 2 months now in about 6 departments with 50 users. Since that time 6500 issues have been created with 20,000 emails sent to 1600 unique recipients. We are still in evaluation mode. If Eventum demonstrates that it can handle the large enterprise, which it has to date, I expect to add an additional 20 departments and doubling it's monthly ticket volume.

My current database size after 2 months is about a gigabyte in size. This is due to the fact that I am allowing up to 10 megabyte attachments. Once other departments are added, I expect the size to grow to one gigabyte per month. I want to keep 3 years of historical data. Will Eventum handle a 36 gigabyte database?

I expect the answer to be yes, since MYSQL has shown to be capable of handling large row counts. The size comes from the blob data, not the row count. After 2 months the eventum_mail_queue table only has 322,000 rows. This is the table with the most rows by far. With my projections this would be the largest table with 13,000,000 rows after 3 years.

I don't show any performance degradations since the day Eventum was brought up. Average CPU utilization is less than 5% for the server that runs both the MYSQL database and the web site during core business hours. The site has had about 1.5 million hits and 100% uptime. I'm running 1.6.0 right now on WIMP (yes, WIMP).

What do you guys think? Is there a size/performance wall out there?