Update 4.4.2 is slow and causing site to go up and down, changed to 4.40.3 and seem much better

6 months ago
hkbits wrote:
The site is now live with 4.40.3 -
https://pikantunder-v44.azurewebsites.net/
Still feels slower than production on 3.8 which is on the same service plan(Server)

The service plan in azure is at Premium V2 (P1v2) - 1 instance.


4.40.2 was not stable and slow,
Was actual waiting about 2min or longer to see pages load.

4.40.3 is way better,
I never benched marked against 4.0 that I was using prior

I'm running it on a B1 plan in Azure, it loads and runs well for with this and had it going for years.
Im about to go multi store and then I can upgrade that instead of two on B1 Plans could go P1 as you have
6 months ago
untiedshoes wrote:
You might be aware but your filter isnt working. Probably because of your custom tag cache helper?

http://nop440.socksandboots.com/shoes

Yeah, it's just a site that I used for load testing, so will never be used anyway :)


How is 4.40.3 (or just 4.40) doing compared to 4.2 with heavy load now?
6 months ago
hkbits wrote:
How is 4.40.3 (or just 4.40) doing compared to 4.2 with heavy load now?


I haven't load tested it as I've been busy with other stuff I'm afraid.

You can quite easily test yourself with https://loader.io and use their free plan.
6 months ago
untiedshoes wrote:
How is 4.40.3 (or just 4.40) doing compared to 4.2 with heavy load now?

I haven't load tested it as I've been busy with other stuff I'm afraid.

You can quite easily test yourself with https://loader.io and use their free plan.


This seems bad? https://bit.ly/3fXODY2
6 months ago
hkbits wrote:
This seems bad? https://bit.ly/3fXODY2


Yeah, that's not great?! Make sure you have the timeout in the test set to 30s (normally the server default.)
6 months ago
untiedshoes wrote:
This seems bad? https://bit.ly/3fXODY2

Yeah, that's not great?! Make sure you have the timeout in the test set to 30s (normally the server default.)


This is the server - almost no load in that period.. at about 25% CPU. Memory steady
6 months ago
Are you using distributed cache at all?
6 months ago
https://bit.ly/3dN75jx - with 30s timeout.

I tried using the site while the test was ongoing now. 20s+ refresh on frontpage.. impossible to use. with only 100 clients over 1 min..


untiedshoes wrote:
Are you using distributed cache at all?


Nope. Ive tried that before using redis, but nop has never been any good at that.

Isnt nop using memory as cache on default anymore?
6 months ago
hkbits wrote:
Isnt nop using memory as cache on default anymore?


Yes, but just wanted to check that 'you weren't' using distributed ;)

A lot can come down to server specs mind you, but I would have thought 100 clients over 1 minute wouldn't cause an issue?!

In my tests, I was doing 150 / 200 clients per second using 4.40.1, but the server is a bit of a monster.
6 months ago
We are using service plans which nopcommerce should pay attention to. Its probably the future for most developers.

We are currently using this:


and a sql server with:


The sql server wasnt under load at all in the test period.