See that on my face? It’s egg. Which is especially gross, as I’m vegan. But that’s what happens when a one-letter typo in your plugin adds about 30 extra database queries to run on every single page load — in both the front-end and back-end — of a WordPress install.
I made a number of architectural changes to GigPress in version 1.4, and one that apparently didn’t get as thorough a review as it should have was the upgrade function that checks to see if anything needs to be added to GigPress’ database tables. Hence the typo. Hence the piss-poor performance that some of you have seen. (Why this only affected some hosts and not others I don’t fully understand … perhaps some sort of SQL caching at work?)
So please, everyone, upgrade to version 1.4.4 and let me know if it resolves your performance problems (well, the ones related to GigPress that is – if you want help with your other, more personal performance problems, that costs extra). I’m still looking for someone who might review how GigPress builds its queries to see if we can bring the number of queries down however.
This version also adds a couple of new small features and a couple of new translations — see the release notes for details.