Extend the time allowed for loading a page?

[200dogz]

Hi,

It seems that when my website tries to load an extremely large request (in my case, a extremely large report generation), it would load for a while, then ask for authentication detaills a couple of time (which should only be needed when first entering the site), and then the server would just die and had to be restarted.

Most of the time is taken on quering databases with OdbcConnections .

Is there certain settings that I can change to allow longer allowance time, or other way to fix this?

Any help is appreciated :)



Billy


ps. just out of curiosity; does anyone know when a website is compiled, where are the "compiled stuffs" actually stored?

[Frinavale]

You can extend the execution time in the web.config file.
Set the httpRunttime executionTimeou t to be larger
For example
[code=xml]
<system.web>
<httpRuntime executionTimeou t="900" />
</system.web>
[/code]

[Frinavale]

ps. just out of curiosity; does anyone know when a website is compiled, where are the "compiled stuffs" actually stored?

It depends on if you have precompiled your website.
If you have not precompiled your ASP.NET pages they are interpreted (not compiled) at runtime.

If it is precompiled, a DLL with the same name as your assembly will be created and placed into your bin folder. This DLL is then used to serve your web pages.

I think that even if you extend the execution time out value, you're still going to be experiencing problems. It sounds like you worker process is being recycled because it's growing too large. You should look into whether or not this is happening.

[200dogz]

It depends on if you have precompiled your website.
If you have not precompiled your ASP.NET pages they are interpreted (not compiled) at runtime.

If it is precompiled, a DLL with the same name as your assembly will be created and placed into your bin folder. This DLL is then used to serve your web pages.

I think that even if you extend the execution time out value, you're still going to be experiencing problems. It sounds like you worker process is being recycled because it's growing too large. You should look into whether or not this is happening.

Hmmm yep you're right.

Changing the execution time does not solve the problem. It still asks for the username and password around every 10 seconds when loading it.

Also, I've recently moved my site to a new server. It was running very fast at first, but after a while it became really slow as if it's compiling the whole website for every page it loads. The debug option's turned off, and it isn't the performance with the hosting server because other websites run fine on it.

I guess I'm not providing enough information :( ....does anyone know any common cause that makes an ASP.NET website really slow and disconnects often?