We are having a difficult problem and looking for some suggestions. Our setup is:
Webserver: Windows Server 2003/IIS 6.0
DB Server: Progress V9.1D on Unix
We have recently started having some terrible performance issues. Internally, our web pages load quickly and without issue. Externally, we have intermittent performance problems that will lock up the browser and eventually time out. I don't see any error messages in the log files(IIS or Webspeed logs).
The odd thing is that you can go to a page 10 times and most of the time, it will be fine, but a few times it will lock up and just spin. So, it's not that one certain page is a problem, because it could be any page. Usually when it locks up, if you just refresh the page, it loads fine.
I've loaded httpwatch to see what components are loading, but it never seems to be the same component slowing down.
Has anyone else seen this kind of behaviour? Or does anyone have any suggestions where to check next? Been a Progress programmer for many years and it doesn't appear to be a coding issue, but can't put my finger on the cause.
Thanks!
Scott
Webserver: Windows Server 2003/IIS 6.0
DB Server: Progress V9.1D on Unix
We have recently started having some terrible performance issues. Internally, our web pages load quickly and without issue. Externally, we have intermittent performance problems that will lock up the browser and eventually time out. I don't see any error messages in the log files(IIS or Webspeed logs).
The odd thing is that you can go to a page 10 times and most of the time, it will be fine, but a few times it will lock up and just spin. So, it's not that one certain page is a problem, because it could be any page. Usually when it locks up, if you just refresh the page, it loads fine.
I've loaded httpwatch to see what components are loading, but it never seems to be the same component slowing down.
Has anyone else seen this kind of behaviour? Or does anyone have any suggestions where to check next? Been a Progress programmer for many years and it doesn't appear to be a coding issue, but can't put my finger on the cause.
Thanks!
Scott