Getting a Low Server Memory-Failed to load PurePaths data
Quick Question: we are running a pretty active dynaTrace server with around 450 agents on it; 12Gb RAM for dynaTrace; 64Mb for the ReservedCodeCacheSize; 256Mb for permgen.
We are getting a dynaTrace error on the client PurePaths dashlet saying "Low Server Memory: Failed to load 'PurePaths' data", and we can't see any data as a result. First the methods disappeared and now we can't see any purepaths at all, even though there's lots of traffic trying to come into the server.
What should we do to address this?
James,
This will happen if you have many people using the dT client, trying to do PurePath-based analysis (anything under the Diagnose Performace cockpit option) over long(-ish) periods of time. In addition to all the work the dT server is doing processing incoming data, those sorts of analyses will read data into memory and compete for heap space. That leads to the "Low Server Memory" warnings.
The best way to address this is to use PW-based charts, or perhaps incidents, to target/refine the PurePaths (and related data) that you are browsing. Diving straight into PP data and then drilling around in a 450 agent system is going to consume significant resources.
Rob
I get the memory management challenge. We have on average 11-13 clients hitting our server, each working with different profiles/different systems. There are around 500 agents hitting the server, spread out across 55 profiles. So getting the user base to shift how they are using the product won't be quick or easy.
Two questions: how can I get alerted when this is occurring, so we know that the server is under stress. And will either increasing the heap memory allocated to the server or upgrading to 5.5 help with this?
Hi,
There is an out of the box incident rule "Low dynaTrace Server Memory".
Upgrading to 5.5 is definitely a good idea as the performance improvements compared to 5.0 are ~25%.
Klaus
We do face the issue pointed out by James, We have the same server configuration with 650 agents, 15 - 30 clients. We also face the analyze purepath load issue. Something which we have been trying is to store the session and move the session to another dynatrace server for deep purepath analysis. Currently we don't do it that often as moving session files is a manual process. Current system doesn't allow us to save the stored session directly in a different location than the live session.
We have opened and RFE to solve this Option to specify different path for continuous session and store sessions.
This way we could restrict the purepath analysis on the primary server to only the live session data and direct all deep analysis to the secondary dynatrace server.
-Sreerag
