Questions that are too localized (such as syntax errors, code with restricted access, hacked sites, hosting or support issues) are not in scope. See how do I ask a good question?
Closed 5 years ago.
Improve this questionThis is my first time posting to this forum for help in the last 4 years of using WP.
Getting to the point - I am experiencing an initial lag when I update a post in the wordpress dashboard.
I checked for slow queries using query monitor but there are non. The longest query takes about .0063 seconds. It is related to options with autoload on. I even tried to create an index for the options but it didn't help.
here is screenshot - .jpg
Now the query monitor shows the post is updated in 1.23 second but in real use it takes about 15-20 seconds to update the post.
Now I opened the Google developer tools to see what was happening - and it shows that the post.php takes around 5-6 seconds initially to respond which is long.
Screenshot - .jpg.
So I have been scratching my head for almost 7 days now to figure out the reason why there is an initial lag but unable to do it.
I am running the site on a VPS with 4 GB ram and 2 Cores + ssd. Nginx+Php 7 + memcache and Fast CGI.
Also, have CF cdn and have disabled dashboard in page rules.
Any expert has some guidance on how to find out the reason for the initial delay - can please share with me.
Will be really happy to get some help on this.
Closed. This question is off-topic. It is not currently accepting answers.Questions that are too localized (such as syntax errors, code with restricted access, hacked sites, hosting or support issues) are not in scope. See how do I ask a good question?
Closed 5 years ago.
Improve this questionThis is my first time posting to this forum for help in the last 4 years of using WP.
Getting to the point - I am experiencing an initial lag when I update a post in the wordpress dashboard.
I checked for slow queries using query monitor but there are non. The longest query takes about .0063 seconds. It is related to options with autoload on. I even tried to create an index for the options but it didn't help.
here is screenshot - https://pasteboard.co/IiEPROz.jpg
Now the query monitor shows the post is updated in 1.23 second but in real use it takes about 15-20 seconds to update the post.
Now I opened the Google developer tools to see what was happening - and it shows that the post.php takes around 5-6 seconds initially to respond which is long.
Screenshot - https://pasteboard.co/IiEP8NM.jpg.
So I have been scratching my head for almost 7 days now to figure out the reason why there is an initial lag but unable to do it.
I am running the site on a VPS with 4 GB ram and 2 Cores + ssd. Nginx+Php 7 + memcache and Fast CGI.
Also, have CF cdn and have disabled dashboard in page rules.
Any expert has some guidance on how to find out the reason for the initial delay - can please share with me.
Will be really happy to get some help on this.
Share Improve this question asked Jun 9, 2019 at 19:42 user3926900user3926900 11 bronze badge 3 |2 Answers
Reset to default 1First you need to find where does the code slow down, try:
- Deactivating all plugins and then check speed. If this works, re-activate them individually( one-by-one ) to find the problematic plugin(s).
- Switching theme then check speed.
- Transfer the theme and plugins to a new WordPress that installed from scratch, then check.
Then write the results.
In addition to what @Rimarx has already suggested, another possible cause (among many) is with the Updates API making external calls which eventually timeout, you can try setting this in your wp-config.php
:
define('WP_HTTP_BLOCK_EXTERNAL', true);
define('WP_ACCESSIBLE_HOSTS', '*.wordpress');
If this works, it is possibly a plugin or theme checking for updates on a slow update server, or where the connection to it is timing out. Again, just one thing to check / eliminate. (If it does make a difference, you would have to narrow down which plugin / theme is causing the issue and go from there.)
发布者:admin,转转请注明出处:http://www.yc00.com/questions/1745421757a4626996.html
traceroute
to get where it restains. – Max Yudin Commented Jun 9, 2019 at 21:59