This is the first ever report of any performance problem with mojoPortal so I'm reluctant to believe the code is at fault though I'm happy to try and help diagnose the problem.

Is the site public where I could see the performance?
Is there anything unusual in the /Data/currentlog.config file?

Is your host doing any resource throttling, ie limiting you to x MB of ram?
My best guess would be that this is whats happenning, your host is limiting you to x amount of ram or limiting the app pool to x amount of ram or the app pool is configured to restart if ram reaches x amount and x amount is not much.

Or it is possible that your site is running in an app pool with other sites and they are running code that is exhausting resources or constantly causing the app pool to recycle.

Hope it helps,

Joe

It has an application or it would not work. I don't know whether changing settings on your host will fix it because I don't know what is causing it though I am 99% sure its a hosting issue since no-one else has ever reported a problem like this.

You did not answer whether there is anything in the log file of interest.

Other than resource starvation which could cause this, one other thing I've seen before that can cause this in web apps is if the db is on a different machine and there is some slowness in resolving the dns name for the db machine.

Both of these are issues to take up with your host.

I just got this error on your site which would seem to indicate a poor connection to the db:

Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

Exception Details: System.Data.SqlClient.SqlException: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.

Source Error:

An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.

Stack Trace:

[SqlException (0x80131904): Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.]
mojoPortal.Web.Global.HandleException(Exception ex) +438
mojoPortal.Web.Global.Application_Error(Object sender, EventArgs e) +94
System.EventHandler.Invoke(Object sender, EventArgs e) +0
System.Web.HttpApplication.RaiseOnError() +182