Showing results for 
Show  only  | Search instead for 
Did you mean: 

Purepath buffer size



Where can  i change the settings for the purepath buffer size  in dynatrace server v5.5


Dynatrace Leader
Dynatrace Leader

In the dynaTrace Server Settings you have to increase the server memory setting. The more memory you give the server the more it will use for the purepath buffer.

This is one way to get more PurePaths into the "Live Session". Another thing to look at is to reduce the length (size) of PurePaths. We often see installations with PurePaths that have several thousand nodes on average - typically caused by overinstrumentation. dT 5.5 also provides new features such as the DB Aggregation that can be turned on throught the ADO.NET and JDBC Sensor. it will greatly reduce the length of the PurePath. Also - have a look at your exceptions and log messages. You might be able to exclude certain exceptions that dont give you value from being captured also resulting in shorter PurePaths and with that opening up more space for other PurePaths to fit in the Buffer


Actually the support recommended me to reduce the buffer size but now the case is closed ,i will see if reducing the server memory helps in my case.

Dynatrace Leader
Dynatrace Leader

Alright - I wasnt sure whether you need to increase or decrease the size - but - at least you know where to change the memory setting.

Keep us posted with your outcome

Dynatrace Pro
Dynatrace Pro

There is a balance between memory required to properly process incoming PP data, and memory required for processing data for analytics (driven by users using the dT client), especially in high-volume applications. I've been fine-tuning this at large customers with good success, pushing the PP buffer lower while keeping the heap size higher, and still avoiding costly GCs on the dT server. If support was suggesting that you push the PP buffer size lower, perhaps they were taking you down this path. If you have a high-volume app, I'd suggest that you reopen your case to discuss this with them. They can share a parameter that lets you control the PP buffer size directly without having to raise or lower the dT heap.

And of course Andi is correct by saying that you should do all you can to control overall PurePath length by removing over-instrumentation, etc.



Exactly i am more concerned about the memory required for analytics and would not want to affect the processing of incoming data and it was obvious that reducing the heap memory would affect the later.

I got a reply from the support  regarding the buffer size parameter and will update you guys regarding its results.

One Best Practice that I've seen some customers do is to install a separate dynaTrace Server that is purely used for stored/offline session analysis. This server wouldnt require a license and is really just used to "host" sessions that you export from your production enviornment. Those groups that need to access the stored sessions can then analyze these sessions on that server without impacting any CPU or Memory resources on your prod server

Well our scenario is that we need to have up to date xml exports for the dashboards to be used in a third party reporting application,and the above solution would require extra mechanism to periodically export in case there is a reliable solution to do that.


Hi Rob,

Have stumbled on your post while looking for more information regarding PP buffer size. Regarding point mentioned by you "I've been fine-tuning this at large customers with good success, pushing the PP buffer lower while keeping the heap size higher, and still avoiding costly GCs on the dT server".

Can you provide some insights regarding typically what steps / or what you look for,  to reduce PP buffer size.


-Thanks, Ankur

Hi Ankur,

What version of dynaTrace are you running?  Here is my advice per version:

  • <= 5.5: If you feel it is necessary to tame your PurePath buffer due to long running GCs on the dynaTrace server or even skipped events or PurePaths due to not enough memory (check your logs) then you have two options.  Reduce the PurePath buffer as Rob says is a "debug" flag on the dynaTrace Server so I would recommend opening a ticket with support for guidance here.  The second option is to upgrade.
  • 5.6: A new (default) setting was introduced for high-volume environments, on the storage page of the dynaTrace Server Settings, there is a radio button to select "Optimize for dynaTrace Server Throughput" which effectively shuts off the PurePath buffer completely.  This is effective in some of my higher-volume clients where the PurePath buffer duration is only about 30 seconds anyway.
  • 6.0 (not yet released as of this writing): This should be a non-issue in future versions of dynaTrace as the component which does analysis for users and the component which does the processing of incoming events are now separated into two distinct running processes, allowing for the increase in throughput you desire.

Hope that helps,

Rick B

We are facing similar issue. Would open case for this. We are using 6.1.


Hi Rick,

Thanks for detailed explanation. I am using dT v 5.6. For custom PP buffer setting will ask customer to wait till v 6.0



Can you please provide the purepath buffer parameter..?

Hello @chiranjit D.

Open/Edit the System Profile > Agent Group > Agent Mapping > Agent Alias/Name > Advanced

Review the below post before any changes.