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?