How do I limit java.exe memory?

Matt,

You can change the memory allocation of your collector by editing the dtcollector.ini file located in your dT installation folder and modifying the value following the parameter "-Xmx".

Please note that it is not recommended to have your collector running on the same machine as your agent as it might uselessly put some load on this machine.

Chris

Chris,

The folks at dynatrace recommended we run the collector on the same server to reduce start up time. 

I see it was set to 2G but I dropped it down to 500m.

Thank you

If startup time is the absolute most important thing you can put the collector on the monitored machine, as that will remove network round trips. Normally however the collector is installed on a separate machine on the same subnet, "close" (network-wise) to the monitored server. As you noted, putting the collector on the monitored server consumes resources on that server.

Note that 500M is not a recommended or supported heap size for a collector. It may work since it seems you have just one agent connecting to it, but keep this in mind if you see odd behavior (dropped events, etc). 1GB is the recommended heap setting even in a "tiny" installation.

Rob

hi Matt,

the memory consumption of the monitored application does not in any way correlate to the memory needed on the dynaTrace Collector. however, the number of connected dynaTrace Agents, the level of instrumentation and also the amount of capture data does.

500 MB is not very much, but for 1 Agent it should be fine most of the time. so if you really only have 1 Agent on this Collector, it sounds weird that you would need so much memory on the Collector.

if you could attach the Collector log - or better: a system information archive - we could take a look at it and maybe get an idea, what's going on here.

best, Christian