Optimising Redis is all well and good if you are running multiple nodes. We have had 2 sites on Azure and neither use Redis. The elephant in the room is the synchronous calls to blob storage to check if thumbnails exist, I've short circuited this problem by caching the existence of the requested thumbnail and using a CDN to deliver them. The general chatty nature of the database calls I've got around by moving everything to an azure VM. It's more admin and you loose the elastic benefits but the site is now blistering fast.
Sounds great but i really want to avoid using VMs.
Me too, hoping to move back to a web apps if nop v4 can solve this but at the moment you can't run a serious nop e-commerce site as a web app. Have raised numerous work items.
Me too, hoping to move back to a web apps if nop v4 can solve this but at the moment you can't run a serious nop e-commerce site as a web app. Have raised numerous work items.
How powerful VM would i have to use in order to host 7 stores with about 30 concurrent users on each site? At black friday that number probably rises to above 100 concurrent users per site.
Are you talking about 7 instances of nop or 1 instance using the multi-store feature? to be honest we have not load tested the live site, we had unacceptable response times with a couple of concurrent users when hosting as a web app on the S3 plan and standard SQL. We now run the equivalent resources on a single VM. If you aren't happy optimising the code I would stay away from storing thumbnails in blob storage or the database, leave them on the web server if you have the space. I also customised the code so the images are served to the client via a CDN which I have raised a work item for. The thing to realise is, nop was never designed from the ground up to use a PAAS architecture. These things have been contributed later. That's why I'm hoping nop 4.0 will see a serious overhaul of the code to resolve it.
For reference
www.openforvintage.com is running on a single VM with my code optimisations, blob storage thumbs and CDN (category pages load in around 1.5 sec when cached)
www.craftrage.com is running on an S2 wep app with SQL Azure no optimisations and thumbs on the web server (category pages load in around 3.5 sec when cached, you can double this if storing thumbs in blob storage)
both use base themes and plugins from nop-templates
Thank you! Yes, this is 7 different stores, where 1 store has 4 multistores. We will try some load testing later today i think. I too hope that nop takes the future seriously. No one is going to use VMs in the future.
no problem, if you end up using sql azure you might want to have a look at elastic database pools to control cost, it will basically distribute sql resources across multiple databases at different load times rather than dedicating fixed resource to all of them.
no problem, if you end up using sql azure you might want to have a look at elastic database pools to control cost, it will basically distribute sql resources across multiple databases at different load times rather than dedicating fixed resource to all of them.
We are using elastic databases for all our websites(150+) and 7 webshops(nopcommerce).
Me too, hoping to move back to a web apps if nop v4 can solve this but at the moment you can't run a serious nop e-commerce site as a web app. Have raised numerous work items.
Now that nop is 4.0. Is it safe to use App & Azure Sql instead of VM? Do you have updates on the performance when use Azure WebApp & Sql & Blob storage?
Me too, hoping to move back to a web apps if nop v4 can solve this but at the moment you can't run a serious nop e-commerce site as a web app. Have raised numerous work items.
Now that nop is 4.0. Is it safe to use App & Azure Sql instead of VM? Do you have updates on the performance when use Azure WebApp & Sql & Blob storage?
Also looking for an update here - how is performance on Azure?
