19 Mar
2013
19 Mar
'13
1:32 p.m.
Indeed, the http://time.ly/ plugin (as they've recently turned it into a
"freemium" plugin) is no longer desirable IMHO. Luckily, we have everything
under the http://sudoroom.org/ai1ec_event/ URL, so we can just make a hard
rewrite to the calendar http://sudoroom.org/calendar and start fresh with a
new plugin. However, we want to make sure the .ics feed still works, so we
need a replacement with an .ics export feature that will allow us to
continue syndicating events. Any recommendations?
There's a varnish plugin
http://wordpress.org/extend/plugins/wordpress-varnish/
but we could also run memcache with batcache
http://wordpress.org/extend/plugins/batcache/
either way we can do better php caching with this
http://wordpress.org/extend/plugins/apc/
On Mon, Mar 18, 2013 at 5:57 PM, William Budington <bill(a)inputoutput.io>wrote;wrote:
Hey, I just wanted to bring this to your collective
attention:
The calendar plugin we have on the wordpress site currently is pretty
terrible. It's the one we have on the Occupy Oakland site, and it
brought the site to a grinding halt. This had to do with the way the
plugin generated its MySQL queries, which was pretty labyrinthine. If
my memory serves me, Mark Burdett rewrote part of the plugin to optimize
indices on the table storing events. We might want to have a look at
that before this becomes a problem.
I've also installed varnish on the server, and I'll be looking into a
good way to cache these pages and serve them from memory so we don't
have Apache/PHP hitting the disk and generating the page every time.
I've done something similar for other wordpress installs, including ones
being actively DDOSed, and it helped enormously.
Bill
_______________________________________________
sudo-sys mailing list
sudo-sys(a)lists.sudoroom.org
http://lists.sudoroom.org/listinfo/sudo-sys