My guess would be that you have a lot of collections on your incidents. When you save the incident, it saves all of the data related to the incident and that can be a lot of data if you have a lot collections, and thus it takes longer to send it across the wire. Check out this article about identifying collections and cleaning them up.
1 of 1 people found this helpfulDaniel,What OS are you running on your IIS server and what are it's specs?We were having some similar issues with our IIS server and had to rebuild it with Windows Server 2003 Standard x64. I asked for the Enterprise edition (per support), but our Server Engineers built it on Standard for some reason. We also increased the RAM to 8gb.We were originally running our IIS server on Server 2003 Standard with 4gb RAM. This configuration was constantly maxing out the memory usage of the w3wp.exe process, causing timeouts and delays. The new OS and RAM configuration has helped performance both in the Portal and Console.Chris
Our IIS server is currently Windows Server 2003 Standard with 2x CPU and 2Gb RAM.
I have been contemplating uping the RAM to 4Gb, but we have noticed that we are not maxing out the RAM yet.
I've already removed all of the problem collections. There is still the occasional "Maximum Request Length" exceeded message, but I believe this is the Service Desk trying to add attachments larger than 4Mb.
I have just removed the CopySettings (which never worked from day one) from the Incident module and this has helped a little.
I'll check the resource usaged on our IIS server with our VMware guy to see if resource usage has gone up recently.
The problem was due to database index defragmenting and updating stats.