Silas2
asked on
Keep Web Application in Server's Memory
When running on Asp.Net app at an ISP in a shared application pool, I notice quite predictably that there is quite a lot of latency when you make a first request but once the servers get going the performance increases considerably. I don't know if it is considered underhand to encourage the ISP's application server to keep your application in memory by having an aspx page constantly open which makes periodic/pulse requests (perhaps for itself?)
Does anyone else do this? How frequent would you make the pulses to get the right balance between keeping the servers alert and not overloading your application? Is IIS clever enough to realise that the same page is being requested, so it wouldn't keep the whole application in memory so you would need to pulse pages randomly?
Does anyone else do this? How frequent would you make the pulses to get the right balance between keeping the servers alert and not overloading your application? Is IIS clever enough to realise that the same page is being requested, so it wouldn't keep the whole application in memory so you would need to pulse pages randomly?
If you don't have fully control of IIS the host system might reset the application pool memory in the early hours anyway.
The web application itself won't be able to keep refreshing the page. IIS sits passively waiting for requests for web pages. If you don't have direct access to the system to run a scheduled application or webservice you can't trigger page loads. You'd have to do it with an external application.
The web application itself won't be able to keep refreshing the page. IIS sits passively waiting for requests for web pages. If you don't have direct access to the system to run a scheduled application or webservice you can't trigger page loads. You'd have to do it with an external application.
ASKER
Sorry, I meant having an aspx constantly in a client browser somewhere in the world periodically (on a timer say 5-10 seconds) poking a request at a specific aspx file within the site which wouldn't do any work but would make IIS keep the site/app in memory.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER