Calcium is overloading the server! What can be done?
The most common reason for this is that a web robot, spider, or other program is accessing the calendars and following all links, resulting in a large number of requests to the calendar in a short time. You can check the access logs for your site to see what sort of requests are coming in; if it is a robot/spider problem, there are two solutions. First, you can set security on your calendars to require logging in to see them. Or, you can try blocking robots using the standard “robots.txt” file, or by configuring your web server. (E.g. using “Deny” in apache.) Another reason Calcium can be CPU-intensive is if a calendar has a very large number of events. If that’s the case, you might want to consider deleting old data that you don’t need; that would help reduce the load. An easy way to do that would be to go to the “Settings” page for a calendar, and click the “Delete Events” link. That will show a form you can use to delete all events in a date range, e.g. from Jan 2001 through Dec. 20
