J
jbijker
Guest
We're running OE 11.7.2.0.1497 64-bit on Redhat 6.10 with classic WebSpeed web agents. The problem we have: Web agents get progressively slower during the day. Web agents memory usage progressively increase during the day. We've increased the memory on the server so it does not start to swap, but performance still degrades over time, which means it's not linked to swapping. When you trim an agent performance is back where it was at the start of the day, so it shows it’s something with the agent and not load on the box. This is happening on a production environment, but we can reproduce on a test environment by doing a bulk run on a specific program. So we did some testing on the test environment as explained below. We’ve made use of Progress.Database.TempTableInfo:GetVSTHandle to check all temp-tables on the system. We've checked for TTs building up records over time. There are lots of TT activity, but nothing that builds up. We’ve also increased the memory allocated to temp-tables so that it doesn’t swap out to disk, but this didn’t fix the memory and/or performance issues. We’ve used the -y startup parameter with the SHOW-STATS command to write stats to client.mon. It reports on local buffer usage, stack size and r-code execution buffer, but all these figures stay more or less constant. No evidence of things that grow. It also shows reads and writes to TTs, but obviously these figures increase over time. Finally we’ve used Progress’ DynObject messages to trace memory leaks. When an agent starts up we do find memory allocations with no corresponding deallocation, but that's because the way we start up our application and all these allocations happen at the start of the agent. There are no other memory leaks we could find. Does anyone have some other ideas we can try to see what's causing the memory buildup and performance degradation?
Continue reading...
Continue reading...