woodb01

@aakrealtor

Can you provide more details on your fixes? I am having the IDENTICAL problem and I also use Hostgator shared hosting.

1) How did you correct the admin-ajax file so that it only loaded minimal WP resources?
2) What work or tweaks did you do to get great load speeds on Hostgator, especially around the REST API?

If you can point me to the web site or any research you did that would be great. I can usually figure most of it out.

Thank you in advance,
Bill

SAME problem here, it happens repeatedly every single day. The error logs grow very large.

I don’t have the pro version so did you find a solution?

WordPress database error Deadlock found when trying to get lock; try restarting transaction for query UPDATE options SET option_value = ‘1596041642’ WHERE option_name = ‘_transient_timeout_2__2951165530’ made by A_WordPress_Base_Url->cache_lookups, C_Photocrati_Transient_Manager::update, C_Photocrati_Transient_Manager->set, set_transient, update_option

This transient problem is happening ONLY with NextGen’s Transient. None of the others are doing this.

Is there a way to cache just the manifest file, with an expiration so that the REST API is not triggered unless a new manifest is needed (date / time only).

I saw your code on the caching in another post but that does not seem to do much of anything. I’ve set it up and it doesn’t seem to make a difference either way.

Last, would the AMP plugin with PWA help at all with performance? My theme is already mobile responsive and the layout is good so I don’t need layout adjustments. Only looking for performance improvement.

By the way Weston, I really appreciate your dedication and commitment to this plugin and to WordPress generally. I’m more than happy to work as a test guinea pig on a possible resolution.

Okay, after more research I’m not sure how much you can do about it. Apparently there is a known performance issue in the WP core related to REST API processing.

There are a couple of interesting articles on the subject and possible solutions. Even though it looks like it would only work on an individual plugin, maybe adapting something along these lines for PWA might help? Don’t know. I know enough PHP to be dangerous and am not a coder.

Great overview article:
REST API performance

Or this, the second highest vote option looks like it *might* provide a potential solution. Looks like the REST API calls all of WordPress for each call. Unless I am not understanding it, this solution looks like it calls a minimum WordPress instance, processes the API, and then loads the rest of WordPress? Interesting idea.

SLOW WordPress REST API

Finally, I saw this article addressing this issue. It is similar to the ones above but has a little different perspective.

WP REST API too slow

Thoughts? Could any of this be applied to the PWA plugin to improve REST performance?

• This reply was modified 4 years, 8 months ago by woodb01.

Long wait times. On this one however it looks like there is a long wait time for the fav icon which does have a file extension.

Here is the waterfall from the posts

json post

Okay, here is another screen shot. This shows that only the files without an extension are affected by this on the mobile load.

It is impacting just the manifest file and the error templates which do not have any extension. Maybe it is a file server mis-configuration? Don’t know but it seems to have that extension issue in common (iPhone 8 simulation).

manifest file load and error templates

Thanks Weston, as you note, W3C accepts the file without an extension. I am just wondering if the lack of an extension causes slow processing by driving through the entire MIME library on a server? Not sure how a server would recognize the file type MIME association for processing?

It is possible it is conflicting with one of my htaccess optimizations. I have been tweaking the htaccess for performance for the last 5 or 6 years (small tweak here, update there, etc. over several years).

Later tonight I may use a stripped down htaccess to see if that has any impact on load time for the manifest file. At least then it will confirm or eliminate whether it is in the htaccess file.

Here is a link to a JPEG image of the manifest load time compared to the rest of the site (waterfall).

JPG image of manifest load time

See the following post that explains the problem with the PHP version update to 7.3 and load.php on line 141 with MySQL. WordPress may have a bug that needs to be fixed.

https://www.ads-software.com/support/topic/php-7-3-errors/#post-12720824

On your load.php line 141 and MySQL issue, see the following post that explains the problem. You will likely have to work with your hosting provider to resolve this until WordPress fixes this bug.

https://www.ads-software.com/support/topic/php-7-3-errors/#post-12720824

• This reply was modified 4 years, 9 months ago by woodb01.

See the following post that explains the problem. You will likely have to work with your hosting provider to resolve this until WordPress fixes this bug.

https://www.ads-software.com/support/topic/php-7-3-errors/#post-12720824

Found the problem for future reference.

This is a known issue with NextGen Gallery (NGG), by default they use their “resource manager” which results in Autoptimize not “seeing” a lot of the JS. As per the Autoptimize FAQ you can disable the resource manager with this code snippet;

add_filter( ‘run_ngg_resource_manager’, ‘__return_false’ );

wp-includes/js/dist/, wp-includes/js/tinymce/, js/jquery/jquery.js