Why the first conection on the ReportServices its so carrie to much time?If your RS server is inactive for any period of time, all the reportings
services information is flushed from memory, and since its not performing any
tasks, overhead drops to virtually nil. When you access the report server
after it has been inactive, it must load all the services and such.. making
your first visit take a while to load, and subsequent usage very fast. Until
it unloads again.
Hope this helps.
"Javote" wrote:
> Why the first conection on the ReportServices its so carrie to much time?|||Thank you Brinkley but i want to know if theres any way to perform this
waiting area?
redards
Javier
"Jason Brinkley" wrote:
> If your RS server is inactive for any period of time, all the reportings
> services information is flushed from memory, and since its not performing any
> tasks, overhead drops to virtually nil. When you access the report server
> after it has been inactive, it must load all the services and such.. making
> your first visit take a while to load, and subsequent usage very fast. Until
> it unloads again.
> Hope this helps.
> "Javote" wrote:
> > Why the first conection on the ReportServices its so carrie to much time?
没有评论:
发表评论