There is a plugin called the P3 (Plugin Performance Profiler) which you can use to get more detail on which plugins are hogging resource. That may be a good place to start. It may not be what you think it is.
Hi @littlesh
That’s strange. We have many users who have thousands of posts and they seems to be using perfectly.
Can you visit your error_log and send us those errors, there must be some hint in there which can help us identify the root cause.
We are trying to improve with every release.
Hi @ahmedkaludi,
looking through error.log there are no errors related.
Thanks for your reply
@littlesh
hmm…. but the loading issue is still there?
There has to be some log file which might give us some evidence.
@ahmedkaludi I’ve made a rollback to previous version and I’ve noticed a strange behaviour with the new one that may be an issue for the cache plugin.
I don’t know why but Google sends vistors to amp pages adding a var (?usqp=mq331AQCCAE=)
With the previous version an url like http:/www.teamworld.it/blabla/amp/?usqp=mq331AQCCAE= doesn’t make any redirection.
In the last version the same url http:/www.teamworld.it/blabla/amp/?usqp=mq331AQCCAE= causes a redirect to http:/www.teamworld.it/blabla/?usqp=mq331AQCCAE=/amp loading the normal version of the site (and bypassing the static cached version because of the var).
I’ve tested it on two different sites. Same results.
-
This reply was modified 8 years, 6 months ago by
littlesh.
AMP Plugin disabled: load avarage 0.50-1
0.9.62 enabled: load avarage 1.50-2.50
0.9.63 enabled: load avarage 50+ (!)
Hi @littlesh
For some reason the Google is adding usqp=mq331AQCCAE
But it’s very strange that it’s causing the redirect…
Can you please contact us from http://ampforwp.com/support/ ?
So we can do in-depth analysis of it.
@littlesh
I seem to find the issue, here is the ticket reference: https://github.com/ahmedkaludi/accelerated-mobile-pages/issues/1247
It’ll be fixed in this update.
0.9.64 enabled: load avarage 6+ with a few users online. Site is very slow on every change of page.
Re-rollback to 0.9.62: load avarage 1+
I think that something is going wrong with redirections (or drains too many resources on each HTTP request).
Hi @littlesh
Do you know of any way that we can findout the reason, I mean where it’s getting the load or a technical way of tracking all this like an error_log
Maybe we can understand something from it and find the root cause of it.