Show menu Hide menu
Here are the slides from my “Site Performance, From Pinto to Ferrari” talk that I gave at WordCamp SLC 2011 and Wordcamp Albuquerque 2011.
Tags: batcache, hyperdb, memcached, MySQL, performance, PHP, slides, wcabq, wcslc, WordPress
Sat 17 Sep 2011 at 3:19 pm
what happened to “videos”?
Sat 17 Sep 2011 at 3:31 pm
The videos aren’t ready yet.
Sun 6 Nov 2011 at 7:37 am
Hi, just watched the video of the presentation and since I am just in the process of moving a WP installation with 20 sites (which works kind of, but not exactly, like MS) and the first memory usage optimization that I have done is to turn off the innodb in mysql, I was kind of alarmed that you strongly recommend on using innodb instead of myism.
From what I googled by now, it seems that the performance benefits are related to insertion and deletion (and some extra stability) but is it really noticeable difference on wordpress?
Maybe I’m just afraid of change…. but since I’m backing up and restoring right now, I don’t want to add some extra work if I don’t have to.
Mon 7 Nov 2011 at 8:11 pm
Unless you have a specific reason for using MyISAM (and there are a few, but aren’t common for most WP sites) you should always use InnoDB.
Fri 26 Apr 2013 at 2:11 pm
Just watched the video and Love it.
I would really appreciate if you can point me in the right direction on where can I find more information about how to keep the connection open and not let it close and send more than one component in that connection.
Is it something related to mod_concat for lighttpd where we can send more than one css or js in one http request?
Is there any document or an article that talks about it specifically for wp?
Mon 29 Apr 2013 at 12:57 pm
HTTP keep alive perhaps?
Wed 1 May 2013 at 1:06 pm
In your slide 41 I can see that there are multiple resources being sent in single http request.
For example, on 3rd http request from s2.wp.com 6 resources are downloaded in single http request.
I am on linux sever with Apache and use latest wp (3.5.1).
Wed 1 May 2013 at 1:15 pm
HTTP keep-alive is a web server level item, so not specific to WordPress.
Wed 1 May 2013 at 1:20 pm
That was fast. I think faster that Vin Diesel’s car. 🙂 Is there any article or some sort of document that talks about how to do it..
And one more thing. When I clicked on the link that I got in my email with the notification of your reply – chrome game me an error of ssl and I had to click on proceed anyway – Just FYI.
Wed 1 May 2013 at 9:24 pm
Your previous comment caught me when I was checking email. The comment moderation email from WordPress showed up at the same time 🙂
For Apache there is http://httpd.apache.org/docs/2.2/mod/core.html#keepalive
For Nginx http://wiki.nginx.org/HttpCoreModule#keepalive_disable
Both default to enabling keep-alive.
Wed 1 May 2013 at 9:25 pm
The SSL alert is about a self signed cert I’ve been using on the site.
Wed 1 May 2013 at 9:56 pm
Thank you so much Joseph. I really appreciate it.
Your email address will not be published. Required fields are marked *
© 2018 Joseph Scott
Theme by Anders Norén — Up ↑