[EventCalendar] SLOW QUERIES caused by EC3

[Hoboken411]

Am I the only one that experiences this? 

 

All day long, I get massive LEFT JOINS which are the sole source of my SQL
SLOW QUERIES. It brings my database to it's knees and CPU % sky-high.

 

Is there anything I can do to the code that can alleviate this? I don't use
the full calendar, just the sidebar. Is there something I can remove?

 

Does it make a difference if I choose "All day" versus just a time period?

 

I just don't understand why it needs to perform joins if it only writes to
the table once I save a post with an event.

 

Someone please please help me. I cannot find an alternative sidebar
"upcoming events" calendar like this.


Thanks,
Perry

 

 

From: eventcalendar-bounces at firetree.net
[mailto:eventcalendar-bounces at firetree.net] On Behalf Of Hoboken411
Sent: Saturday, March 08, 2008 2:28 PM
To: 'Support for EventCalendar plugin'
Subject: [EventCalendar] SLOW QUERIES caused by EC3

 

Hello Everyone!

 

I have a relatively popular blog with between 1MM - 2MM pageviews per month.

 

I use EC3 (3.1.0) on a 2.0.11 version of WP.

 

I only use the sidebar function showing the next 10 days of events, that's
all.

 

However, since my site has steadily gained in popularity, I've been
suffering MySQL performance issues. After weeks of experimentation and
analysis, I've come to determine that the EC3 plugin is the source of the
SLOW SQL queries. Without boring you with the exact processes, it seems that
the EC3 plugin is causing frequent high CPU% loads with the heavy LEFT JOINS
in the databases.

 

My questions are simple:

 

1.       If the EC3 plugin creates a table with the URL and date, I would
assume it only has to perform the join when a post is saved with an event.
Why is it continually bogging down the database?

2.       Does filtering cause this? The plugin doesn't delete expired events
for one thing (I constantly have to go back and delete the event from the
original posts from time to time), and what about future events? Does the
filtering (i.e., "if event=longer than 10 days, then do not display") cause
the CPU load?

 

Any advice or suggestions would be greatly appreciated. I love the plugin
otherwise!

 

Look forward to your responses. 

 

Perry

 

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://penguin.firetree.net/pipermail/eventcalendar/attachments/20080310/83a0f191/attachment-0001.html