This project is read-only.

"First" loading takes too much time...

Mar 30, 2009 at 9:06 AM
That's my problem?
Sometime when i'm loading my N2 site, it takes too much time and it seems that site compiling it's sources everytime.
Could someone say me, what's going on with my site?
Mar 30, 2009 at 8:23 PM
How long time is too much? Could you run dottrace or some other profiler tool to analyze where this time adds up?
Mar 31, 2009 at 10:07 AM
It's about 20-30 seconds at first load.
It would be nice if you say me how can I run dottrace?
Mar 31, 2009 at 6:58 PM
Over here, there is a trial version you can use.
Apr 1, 2009 at 5:22 PM
Edited Apr 1, 2009 at 5:32 PM
I have tried this profiler and there is it's result:
(download it here, JetBrains format)
Hmm, it seems normal, but this profile from my local server.
I can't start profiler on hosting server.
Apr 1, 2009 at 7:20 PM
Sorry, can't spot anything. Over here a recompile usually implies a 10-15 second break.
Apr 1, 2009 at 7:25 PM
How could I avoid a recompile break?
It can happen every hour!!!
I saw ping feature in web.config file, but feels like it's dont work.
Apr 1, 2009 at 7:34 PM
Okay, this is in the production environment. Yes, the ping is supposed to keep the app alive and avoid this.

Is <scheduler keepAlive="true" in configuration?
Try also changing <scheduler keepAlivePath="~/edit/keepalive/ping.aspx"


Apr 1, 2009 at 8:34 PM
Yup, scheduler was turned on!
I have been just set keepAlivePath to on.
But I need some time to test it.
Apr 2, 2009 at 9:32 AM
Libardo, do you think that making of precompiled version should help?
Apr 2, 2009 at 7:46 PM
What's your hosting situation like?  I know that on some shared hosting environments, once your worker process hits a certain memory limit (~100MB) the app pool is automatically recycled - thus forcing the recompile.  Another thing to look into...
Apr 2, 2009 at 9:46 PM
You could turn on some trace logging and see if that reveals anything interesting.

You should see something like "Ping Pong" if the ping is running.