Yes, I have tried only "Stop" and "Start" as well shutting it down and re-running it. The result varies, but overall, pages do load a bit faster but soon degrades within a couple of hours or a couple of days depending on the activity level. Only rebooting the server brings everything back to expected load times. But, it degrades again. The hard part is that I do not see anything in the performance monitor, other than higher paging, that offers a clue. This one is going to take a while.
Sent by FoxWeb Support on 05/29/2006 10:48:18 AM:
Have you tried restarting FoxWeb instead of rebooting? What happens in that case?
Sent by Joe Goldsmith on 05/23/2006 09:13:10 PM:
Well, I assume it's a memory leak. Every now and then while testing I press a button link and the called page comes up slowly and sometimes not with all the CSS or graphics showing. This same issue has been reported by users on my subscription application. I can reboot my work station and it clears up for a while. I can see the same thing happening when using the application on the server directly. This has been going on for over a year and I keep assuming that IIS or the server is misbehaving. Performance monitoring and logs do not indicate an over use of resources except for paging to cache that reaches 50% and hovers between 35% and 40%. I doubled the memory in the server and the paging is much better but the issue mentioned above first still lingers.
Could this be a situation where local or private variables are not being released when changing pages? Could it be a memory leak somewhere? Any ideas?