nopcommerce is very slow at the starting time

This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.
13 years ago
Hello,

I installed the real shopping cart using nopcommerce.
Everything is normal except it takes long time
to load at the beginning. But when the front page is loaded,
the webiste speed is reasonable.

Any suggestion to overcome this issue, friends?

Thanks,
13 years ago
I have installed in shared environment and the first load takes a long time as well.

The load time is unacceptable and we are looking for solutions to overcome this performance issue.

(Version 1.60)
I copied the NopCommerce site to the hoster, ran the install and it all appears to be working fine however it is very slow when hitting the default page (or any).  After I hit the first page, things seem better but the first hit is really really bad.



Any help is very much appreciated.  

thanks -dave
13 years ago
I just installed v1.60 via GoDaddy Hosting Connection. The first load of my default page takes about 60 seconds (very unacceptable) and the admin panel is even longer, about 3 minutes. After those initial loads, everything flies. I've done some reading about possible causes, from GoDaddy's Medium Trust (although why would they offer nopCommerce as a solution if this was the case) to IIS and Godaddy not being able to handle the "keepalive" feature, which was probably meant to solve the slow load issue.

In any case, Godaddy was less-than-helpful when I asked why the system was slow: they just sent me a generic "how to speed up your website" document and closed my case.

These initial load times are totally unacceptable, yet only happen if the site hasn't been hit in a while.

DOES ANYONE HAVE ANY SOLUTIONS TO OFFER?
13 years ago
I discussed with GoDaddy as well and got no help.  The suggest I work with nopCommerce support to resolve the issue.

I am at wits end with regards to how to proceed.

Any help is very much appreciated.

-dave
13 years ago
there are a couple of things you can do.

if you can edit your web.config file, find the line

    <compilation debug="true">

and change it to

    <compilation debug="false">

There is also a keep alive function in nop look here:

https://www.nopcommerce.com/boards/t/1932/how-do-i-configure-keepalive.aspx

https://www.nopcommerce.com/boards/t/1042/abfitnessequipmentcouk.aspx
13 years ago
Both of us above are hosting on godaddy and that level of IIS customization is not available to us.

Is the only other alternative some 'keep alive' service/program that will hit our sites every 20 minutes? (to ensure it stays alive?)

Why would the startup cost be so high for this particular asp.net web application?

BTW, i have already set debug=false in my web.config.

Do you recommend any ping - keep alive type apps for us?

thx-dave
13 years ago
What is actually happening is that your site is being compiled after the ASP.NET worker process has restarted whenever there is a lack of activity on your site. The worker process can restart for many reasons, however the most troubling one is due to site traffic. By default IIS will shut down the ASP.NET worker process after 20 minutes of inactivity meaning that the next request will restart the worker process and have to compile your entire nopCommerce site all over again.

To prevent this, a web request has to be made to one of your pages at MAX every 19 minutes. I recommend that folks take advantage of the built-in keep-alive function in nopCommerce. NopCommerce already has a keepalive Ping page set up in your file system.

For Windows (IIS) Shared Hosting on Godaddy:

1. Register for a free web cron job, try http://www.setcronjob.com or http://www.keepaliveforever.com.
2. Create a new cron job to hit the following page of your site:  http://www.yoursite.com/KeepAlive/Ping.ashx every 10 or 15 minutes


This ping should prevent the ASP.NET worker process from shutting down and having to recompile every time there is a lack of activity on your site.
13 years ago
dyardy wrote:
Both of us above are hosting on godaddy and that level of IIS customization is not available to us.

Is the only other alternative some 'keep alive' service/program that will hit our sites every 20 minutes? (to ensure it stays alive?)

Why would the startup cost be so high for this particular asp.net web application?

BTW, i have already set debug=false in my web.config.

Do you recommend any ping - keep alive type apps for us?

thx-dave


Pretty sure you will find that the issue is NOT nopCommerce ... it's GoDaddy's hosting service! I had the same issues and concerns, and eventually got SO SICK of GoDaddy support blaming everything on "the app" that I ditched them and moved to Arvixe (www.arvixe.com). My site is now SO MUCH FASTER, and also everything works because Arvixe provide a full-trust ASP.NET environment where GoDaddy only support medium trust. You should consider moving to another hosting company.
This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.