[EventCalendar] PRUNING the plugin

Tue Mar 11 09:44:28 UTC 2008

Don't some very high trafficked websites use WP? To the tune of millions of pageviews a day?

Either way, I'll probably give back the customized plugin, however without support...

Sent via BlackBerry from T-Mobile

-----Original Message-----
From: firetree_ec3 at spamex.com

Date: Tue, 11 Mar 2008 06:37:02 
To:eventcalendar at firetree.net
Subject: Re: [EventCalendar] PRUNING the plugin

If your site is that heavily trafficked, then you should probably consider doing (or hiring to have done) some custom work. That is what I have done with other CMS systems in the past. You may or may not want to give back the work you do. If not, try to do it in a fashion that can be easily applied to upgrades. I have modified cores so much that the entire project has branched too far from the mainline to be reintegrated.

Most OSS CMS systems aren't really made to be particularly efficient high-volume transaction processors. WP has a fair bit of overhead. That flexibility and customizability come at a price.

On Mar 11, 2008, at 6:17 AM, Hoboken411 wrote:

* Replies will be sent through Spamex to eventcalendar at firetree.net <mailto:eventcalendar at firetree.net>  
* For additional info click -> www.spamex.com/i/?v=17832931 <http://www.spamex.com/i/?v=17832931>  

Hehe.. not really, I’ve been going nuts studying why this is causing issues. I don’t know how many other high-traffic sites use EC3, but it’s becoming nerve-wracking.

I have all possible caches on my dedicated server. WP-cache, zend optimizer, plugin output cache (for some plugins), php_speedy (relatively new) Varnish and more.. I’ve tweaked the living daylights out of my site (still more to go.. on the my.cnf and httpd.conf and the php.ini end.. fine tuning more or less) and the one slow query is the EC3.

I have a guy looking at possibly modifying the code where it caches the output once per day (that’s all I need) and re-runs the query then. Because often times throughout the day, my server crawls for a few minutes while it performs giant MySQL queries for EC3…

There should really be an option in the plugin to determine how often the query should run. Especially if you only have about 50 or so future dates (all day events)…

From: eventcalendar-bounces at firetree.net <mailto:eventcalendar-bounces at firetree.net>  [mailto:eventcalendar-bounces at firetree.net <mailto:eventcalendar-bounces at firetree.net> ] On Behalf Of Mark Naylor
Sent: Tuesday, March 11, 2008 5:34 AM
To: Support for EventCalendar plugin
Subject: RE: [EventCalendar] PRUNING the plugin

Hi Hoboken,
Part of the problem with no response is when you sound very knowledgeable about table joins etc, people think your knowledge is greater than theirs...
I have no idea what you are talking about.
However, going for the obvious first, have you tried wp-cache? http://wordpress.org/extend/plugins/wp-super-cache/ <http://wordpress.org/extend/plugins/wp-super-cache/> 
If all the queries for ec3 are the same, then they will only get run once?
Good luck
Mark

----------------

From: eventcalendar-bounces at firetree.net <mailto:eventcalendar-bounces at firetree.net>  [mailto:eventcalendar-bounces at firetree.net <mailto:eventcalendar-bounces at firetree.net> ] On Behalf Of Hoboken411
Sent: 11 March 2008 02:56
To: 'Support for EventCalendar plugin'
Subject: [EventCalendar] PRUNING the plugin
Hello everyone again. I’m going to try another angle for my SLOW QUERIES post, which hasn’t seen a response yet..

I only use EC3 in a limited way: Just a sidebar list of the upcoming events for the next 10, or maybe 14 days. It should be updated once a day (at 5:30am).. very simple right?

Is it possible to prune out the rest of the functionality, such as the month view and anything else that may cause heavy MySQL usage?

I understand it needs to make joins when creating the wp_ec3_schedule table, but is it necessary to have all these queries since the table is static for the most part?

My site is in desperate need to performance enhancement…

Any suggestions would be so so welcome._______________________________________________
Blog: http://wpcal.firetree.net/ <http://wpcal.firetree.net/> 
EventCalendar at firetree.net <mailto:EventCalendar at firetree.net>  mailing list
Unsubscribe: http://penguin.firetree.net/eventcalendar <http://penguin.firetree.net/eventcalendar> 

catchall account  
_______________________________________________
Blog: http://wpcal.firetree.net/
EventCalendar at firetree.net mailing list
Unsubscribe: http://penguin.firetree.net/eventcalendar