1.5.1 slow, causes high request time

@janvitos We’ve just published the 1.5.2 release to www.ads-software.com: https://www.ads-software.com/plugins/amp/

Release notes: https://github.com/ampproject/amp-wp/releases/tag/1.5.2

This release includes the bump to the 5000 threshold. https://github.com/ampproject/amp-wp/pull/4513

It also adds the CSS monitoring time series to Site Health debugging info. This will assist with debugging issues related to parsed CSS transient caching getting disabled. https://github.com/ampproject/amp-wp/pull/4519

I’m still going to be analyzing the transients you provided.

That sounds great @westonruter.

I will be installing 1.5.2 soon and I will mark this ticket as resolved.

Thanks!

Hi @westonruter, just to let you know, I just noticed that although the threshold was set at 5000, amp_css_transient_caching_disabled was switched to true again.

After looking at my server monitoring tool, I noticed the request time went back to 160ms once again.

I have just upgraded to 1.5.2 and will be monitoring closely the request time and the amp_css_transient_caching_disabled variable. But if this keeps on happening, I will definitely have to switch back to 1.4.4.

• This reply was modified 4 years, 7 months ago by janvitos.
• This reply was modified 4 years, 7 months ago by janvitos.

Thanks for the update. Could you do another transient JSON export into that Gist, specifically as a separate file. I want to compare to see the new entries after a day.

Also, could you go into Site Health and obtain the AMP info as just updated with the CSS monitoring info as seen in https://github.com/ampproject/amp-wp/pull/4519?

The new transient JSON export has been added to the gist in amp_transients_04032020.txt.

Here’s the AMP info from Site Health:

### amp_wp ###

amp_mode_enabled: reader
amp_templates_enabled: post
amp_serve_all_templates: This option does not apply to Reader mode.
amp_css_transient_caching_disabled: false
amp_css_transient_caching_threshold: 5000 transients per day
amp_css_transient_caching_sampling_range: 14 days
amp_css_transient_caching_transient_count: 184
amp_css_transient_caching_time_series: 
	20200331: 108
	20200401: 172
	20200402: 175
	20200403: 184

Please note that all of this info (both transient JSON export and AMP from Site Health) was collected AFTER the upgrade to 1.5.2. So amp_css_transient_caching_disabled is now set to false and the request time is back to 60ms.

• This reply was modified 4 years, 7 months ago by janvitos.
• This reply was modified 4 years, 7 months ago by janvitos.

Hi @westonruter,

Just to let you know, since upgrading to 1.5.2, amp_css_transient_caching_disabled has never returned to true and request time has been around 60ms (normal).

I haven’t yet had a chance to analyze the transients, but I haven’t prioritized it since you said it hasn’t been an issue. I still want to do it, however.

But I wanted to inform you that v1.5.3 was just released. It includes a button in the Site Health test to re-enable the CSS transient cache, so you won’t have to do it manually via WP-CLI.

I looked at the transients and nothing jumped out at me as being a red flag in terms of the CSS selectors being parsed. So if increasing the amp_css_transient_caching_threshold fixed the issue for you, then I think this is resolved!