Hi,
We were the first company to develop a live, fully responsive, multi-store nop site, running 13 stores in total from one application (nop 3.00) - football clubs shops.
We used to have a lot of problems when the server was under load, so we changed servers, along with an upgrade.
After still having issues, we moved to 4.00 when it was released, along with another server change/upgrade, but we still had issues, specifically when we had kit launches, and the load was on the heavy side (to be honest, we're only talking about 300-500 customers at a time, so not really what I would class as high).
Anyway, we again changed servers, to what we have now:
Dual E5-2620 v3 CPU’s
Dual 1TB SSD in raid 1
64GB ECC ram
Windows Server 2019
IIS 10
MSSQL, with web licence
Plesk
1Gb/s port
We're still experiencing timeouts under load, so thought we'd run some tests on basic installs of both 4.00 & 4.30 - no products, no categories, so really are basic installs!
We've done these tests on very basic installs as our production sites use some bespoke code/plugins, so wanted to see what the load would be live on clean installs.
Here are the results for 4.00.
Timeouts starting at 30s.
Here are the results for 4.30.
Timeouts starting at 30s.
During the tests, for 4.00, nop.web uses around 40%, although, on our production sites, we've seen it as high as 100%!
By the way, we also run other sites, using 3.7, 3.8 and 3.90. One is another multi-store (3.70), and we have a 3.90 with heavy code changes - these all run fine under a 500 load, and all have bespoke code changes/custom themes.
We're at our wits end with this now and would appreciate anyone chiming in, that may have had similar issues?
Regards,
Craig
p.s. We've tried all sorts, including changing the times for scheduled tasks, stopping scheduled tasks completely, but only seem to get a very small improvement, and nothing worthwhile.
We also tried the MSSQL Provider V2 plugin, but had multiple CGI / FASTCGI processes, which loaded up the server.