Wp-admin very slow

New test time:

DISABLED PLUGIN – wp-admin
2,5s
2,6s
2,0

ACTIVATED PLUGIN – wp-admin
3,5s
6,5
4,5

NEW Report number: YAOHHXQP

just one more detail, I have this LITESPEED WEB SERVER page empty:
https://storage.googleapis.com/studio416x-sao-paulo/webserver.png

Is there any default setting, to optimize wordpress + woocoommerce?
Thank you so much again, it will be a great help.

Hi,

please try disable object cache if you have do not seen “connection test: passed”

for that screenshot, please do NOT touch anything in there, let plugin to control the cache behavior

Best regards,

Hi @qtwrk,
Thanks for quick reply.

Object cache everything ok, see:
https://storage.googleapis.com/studio416x-sao-paulo/object%20cache.png

I have several wordpress sites on the same server, do I need to change the number of the database, object cache?

does it work if you disable OC ?

Do I need to do something else? on the server or in the plugin, to improve the loading of wp-admin?

Report number: YAOHHXQP

I turned it off now, but I don’t see any difference. @qtwrk
New Report number: IOVCTYDP

now that has become weird

please try export your current setting , then reset to default setting, see if it helps ?

Hi,

I looked at your report but didn’t find anything obviously responsible for what you are concerned with. I did, however, find something questionable about your crawler settings. I’m kind of surprised that you didn’t report any issue with your crawler. It is this setting: crawler-crawl_interval = 1800 .

“Crawl interval” indicates how long the server should initiate the crawler to crawl the entire site again after the crawl process has started, which is why the default value is 302400 seconds (3.5 days). You set it to 30 minutes, which means the server keeps restarting the crawler process once every 30 minutes, way before the crawler is able to complete crawling your entire site. What is recommended is that you leave the default value and watch how long it takes your crawler to complete crawling your entire site a few times and come up with an average value and then set the Crawl interval value to be just a little bigger than how long it takes the crawler to complete crawling the entire site once. For example, if it takes three hours to complete the process, then you can set it to four hours. Some people mistake “Run duration” to mean how long it takes the crawler to complete the entire process. The way the crawler works is like this: 1) the process is initiated; 2) the crawler runs by the value of the “Run duration”; 3) the crawler stops at the end of the run duration and breaks for the value of “Interval between runs”; 4) Steps 2) and 3) get repeated as many times as necessary until the whole process completes; 5) the crawler process is started again when the Crawl interval is up.

In summary, the sluggishness of your wp-admin could be related to the abnormal settings of the crawler in that it overwhelms the server’s resources and in turn makes your wp-admin slow. Just a thought. Please trying adjusting the crawler setting and see if your wp-admin will improve.

Regards.

@qtwrk
I did this without success.
Only by disabling the plugin things improved.

I’m looking at another site, on the same server: using wp fastest cache, things are going almost in half the time.

Hi,

please create a ticket by mail to support at litespeedtech.com

we will investigate it further

Best regards,

hi @tenkstars
Thanks for this.

I’ll tweak this, but I’m finding 3.5 days, too long for a woocommerce dynamic store.

Is there any other way to warm up the cache, when there are any changes to orders, products?

Thank you very much, I will do this. @qtwrk

Just a question, does the litespeed plugin have any cache or improve something in wp-admin?

Or just on the front end?

Hi,

by theory , object cache could improve bit on wp-admin , besides that, it doesn’t help on wpadmin area

Best regards,

@qtwrk I understand.

Just one thing, is there any way to optimize the woocommerce cache?

What happens, as my customers access the dashboard a lot, just to update order status, create products and sometimes change product inventory, whenever they do something like that, the cache will be flushed entirely?

Do you suggest something, to help me?
Is there any other more effective way to warm up the cache?