Low Client Memory
When looking a purepath tree, I've got a "Low Client Memory; Failed to load "pure path data".
I've already set the memory to 1024, but it is not enough, how increase it ?
thanks
Pierre
Hi could we use client version 6 - 64 bit with server/collector version 5 ?
Unfortunatly this is not possible due to some important and significant changes in our archtiecture that we introduced with dT 6.0
Hi Guenter,
I'm benching a batch process without knowing the good level to put the purepath, then I start purepath at begining of batch but with a few data to process.
Even with node number recorded lower than system limit, I can see the tree node due to memory issue. Furthermore I can't see any other dashlet, I encounter the same error message.
So waiting with impatience the next version 
hi, any feedback ?
should I raise a ticket support ?
Regards.
The 64bit JVM is not officially support in 5.x. With 6.0 we officially support it by providing a 64Bit Client.
So - opening a support ticket on a currently not supported configuration might not be the right way. FYI - dT 6 is coming out next month
Hi Pierre,
Andi has been telling me over and over: Don´t necessarily start your analysis with PP, but narrow down your results first...
Here is a quote from him from the above mentioned DONE thread:
"The goal should be to have PurePaths of a reasonable size. One common reason for very large PurePaths is the number of Database Statements on DB heavy transactions. dynaTrace 5.5 has a new feature called "Database Aggregation". This feature greatly reduces the size of DB heavy transactions - making them viewable again in the PurePath tree without needing a whole lot of extra memory.
also - there are a lot of other dashlets that help you analyze performance without the need to go directly to the PurePath, e.g: Method Hotspot, Database Hotspot, ...
What is the reason why your PurePaths are that big? how big are they?"
Hope this helps to bridge the gap until we release the 64 bit Client with the next version!
G.
I've launched with 3072mo, reduced the number of node registered and record a new run (and Tree node went from more than 1 million to 727816),
but I still have this message while when looking the Windows task manager, the java process doesn't exeed 703 000 K.
What's wrong .?
You can try using 64 bit JVM and increase the memory to more than 1024. Here is the discussion on this topic
DONE: dynaTrace Client out of Memory - 64 bit Client? (Spring 2014)
<64-bit-JRE-Location>\bin\javaws.exe -wait -J-Dcom.dynatrace.client.jvmrestriction.ignore=true -J-Xmx2048m http://<yourserver>:8020/webstart/Client/client.jnlp
.
