Anyone else notice a performance hit after the upgrade? If so, what’s the cause?

I have not noticed anything, can you help me track this down by letting me know specific details, if u noticed with a particular addon or front/backend pages etc.

Not sure what server setup you have but if it’s a dedicated have u tried a restart to clear anything stuck.

Thanks,

Stiofan

The site is hosted on wpengine and tests were run against the staging environment (no cache or cdn). The delay occurs when the core gd plugin is updated. The time to first byte for the /places/ landing page increased from 2.266s before the upgrade to 4.004s after.

The tests were repeated several times to ensure consistency. The production environment is far more performant, of course, but we still noticed enough of an increase in the time to first byte to warrant rolling back the upgrade.

I hope that helps narrow things down, but I’m happy to do further testing if you have anything specific in mind. We can’t upgrade production until this gets resolved.

On a performance-related note, I noticed that gd uses the original image as the thumbnail on listing and search pages, rendered as a background image. I understand the utility of this approach, but it creates a huge performance bottleneck, especially on sites like ours with user-submitted listings. We use the imsanity plugin to enforce a maximum height and width, but this only provides minimal improvement.

We also tested WP Smush.it, which adds an unacceptable delay when saving new listings. The WP Image Size Limit plugin doesn’t work with gd’s front-end image upload form. Is there any other image optimization method that we can implement with gd?

Cheers,
Greg

I tried WP Smush.it first, but couldn’t actually get it to run as it kept timing out (I think, don’t remember for sure). One nice think about EWWW is that there are a number of settings you can make and you can also apply it to images that have already been added. It will tell you the “savings” on the backend as well.

With that in mind, one approach…perhaps, haven’t actually looked to see if this is a viable option… would be to allow the full uploads and then periodically run it across the library. Ideally though, hopefully you could set it and forget it and it would run without taxing the system too heavily.

cheers

EWWW Image Optimizer is on wpengine’s banned plugins list, but the cloud service seems to work like a charm. Thanks for the suggestion.

Cheers,
Greg

Figured it out, it was code added by vikas, i have no idea what he was thinking…

Stiofan

//add_action('wp', 'geodir_temp_set_post_attachment');

Stiofan