Add to cart and uncached pages load EXTREMELY slow after 2.6.0

Ok, you’ll have to let us know.

I sure will. Thank’s again!

See you in this thread on woocommerce 2.6.2

Hi Mike Jolley,

Ok, so I have updated to 2.6.2 again. I still have the same problem.

But you’ll only notice once you have had some traffic to your site.

Hosting support has been on it since the initial upgrade to 2.6. Then I rolled back to 2.5, everything was fine. Yesterday I installed 2.6.2, but the same thing is happening again.

This is how hosting tech are saying what is happening:

– a visitor goes to the site
– some Apache services are starting, but never ending
– another visitor goes to the site
– some Apache services are starting, but never ending
– and so on and on

– After some time all the uncached pages will become very slow in loading, because of the apache that is in a loop. Cached pages are still loading fast of course, but uncashed took up 81 seconds after a night long of doing notthing.

Once Apache is restarted again, all is fine for a while, until there same happens again.

It is since woocommerce 2.6 Never had any problems before. Tried out 2.6.2. Still happening though. Right now I’m back to 2.5 All is well again.

But at some point, I am going to have to upgrade to 2.6?

my site is: https://www.vgpjewelry.nl

Curious about what you think.

“some Apache services are starting, but never ending”

Any idea what these processes are actually doing?

No, I’m sorry.

But it happens when a new visitor access the webshop.. And only after upgrading to 2.6. I’m back at 2.5 for now.

Is geolocation enabled on your store?

How can I check that?

WC > Settings, default customer location setting.

The Default Customer Address is set to shopbasicadress.

It is not set to one of the Geolocation options.

I can set it to the option ‘no adress’.

Might that help? To be honest, I have no clue to what that setting does or is usefull for. Does that setting envoke apache request? And if so, why would it have no impact on WC 2.5x and does cause a problem in WC 2.6x?

Really glad with all your help and suggestions! Thank you so much!

No, just suggested geolocation since that would add extra overhead due to remote calls.

Thanks,

Any other idea’s how I should proceed?

No, I think you’d need to get someone to look at it if the host cannot provide more details. There are no other reports of this I can find.

Ok, thanks for all your trouble and help.

I will contact tech support again and will keep on trying to update each time a new WC release comes out.

ok. If you do have access to another host such as https://pressable.com/ you could run some comparisons if things stay bad.

Hi Mike,

Thank you for your suggestion. I have bookmarked it.

Somehow, this problem seems to have resolved itself. Maybe it was the latest update from woocommerve, maybe the latest update from the theme storefront.

It has been over a week since this probblem has appeared, so I am comfortable to close this thread.

Thanks for looking at this problem with me and giving suggestions!