We periodically experience just the type of slowing you describe. I discovered the following to be the cause:
The Updox connector runs on our server. It should use about 30-40mb of memory (per Updox support). Periodically, that number rises. We have seen it above 600mb at times. When it gets above 200 or so, all the computers using AC slow down.
I know this makes no sense; when I first noted it, no one in our office or at Updox could understand this, nor could they understand why it should slow AC. Everyone is now finally convinced because the problem is recurrent, and fixing it immediately fixes the slowing.
.....
So...the next time your system slows down, check the memory use of the Updox connector, and if it is high, restart it and see if it speeds things up. Please let me know one way or the other; I would like to get Tobin working on fixing it! Some people believe that there is no such thing as a "memory leak" but that is how I would describe this.
Actually could make quite a bit of sense. It could be a 'memory leak', or it could be that the program is holding something in memory that is no-longer needed, and can be cleared. I won't get into Java and 'garbage collection', but those are actually two different things.
I look forward to hearing what memory state you find in the task manager the next time things slow. The performance Tab will show CPU and memory trace, The processes Tab will show processes and allocated memory & current CPU; click the header to sort by memory.
