October 28, 2011 at 12:47 am
[font="Verdana"]How to mitigate application latency experienced in first execution of application(screens) after the complete update of scripts and index rebuilds of database? Especially when the both indexes and statistics were not updated/cared for a long time?
Thanks
[/font]
October 28, 2011 at 12:54 am
If I understand your issue right, this is due to data being flushed out of the buffer cache. This is actually quite normal if you update statistics or rebuild indexes on large tables, and there is really nothing you can do about it (except buying a lot of memory, but one of my customers are not willing to pay for .5TB of memory to avoid this 🙂 )
So, for the solution: You can quite a bit of information using google (or other search tools) looking for "cache warming". Long story short, at the end of the maintenance job, execute queries causing frequently used data to be read into memory again.
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply