There’s been much discussion after the release of version 1.4 regarding the fact that this release seems to be bringing some sites to a slow crawl under certain server configurations. There doesn’t seem to be any rhyme or reason to this, as some of these servers are very similar to my own testing server, where GigPress is performing like a champ.
First of all, I’d like to apologize to all of the users who’ve come to rely on GigPress to manage shows on their (or their clients’) sites, only to have this issue rear its head with an upgrade. I know that sucks.
I’ve collected some feedback that may help me isolate this problem, and am working on it between my insane client workload. I really want to resolve this as soon as possible, and your patience is appreciated. Although GigPress is my free contribution to the WordPress community, that doesn’t give me license to abdicate my responsibility to its users.
Second, I’d like to put a call out to other developers and coders who may be able to help me optimize GigPress further. Although I don’t think MySQL queries are the problem in this instance (as I didn’t really add any new queries), I’m well aware that GigPress’ queries could be greatly optimized by someone who had a greater depth of experience in the art of query-crafting than I. Anyone who has a little bit of time and is interested in making GigPress better, please drop me a line.