Geek asks and answers

New Relics of JVM Graphics on Tomcat

I am currently trying to optimize my Tomcat on a 64 bit server with 4 GB of memory. Here are my current settings and its ticking is beautiful:

-Xms256m
-Xmx1024m
-XX:MaxPermSize=256m
-XX:+UseParNewGC
-XX:+UseConcMarkSweepGC
-XX:+CMSClassUnloadingEnabled

What I don’t quite understand is how they relate to the new relics - the optimal use of the heap of the Eden space - what should I aim to see in the reports? Relay charts

+3
source share
1 answer

The information in the diagrams does not exactly correlate with the parameters specified for the JVM at startup, since the information provided is a trend. Most, if not all, of the metrics used for charts for the JVM are averages for the time period specified in the collector.

, , :

()

  • Memory/Heap/Committed with value_fn: average_value
  • // _fn: average_value
  • // _fn: average_value

PS Eden ()

  • MemoryPool/Heap/PS Eden Space/Committed with value_fn: average_value
  • MemoryPool/Heap/PS Eden Space/Max _fn: average_value
  • MemoryPool/Heap/PS Eden Space/ value_fn: average_value

PS Survivor (MB)

  • MemoryPool/Heap/PS Survivor Space/Committed with value_fn: average_value
  • MemoryPool/Heap/PS Survivor Space/Max value_fn: average_value -MemoryPool/Heap/PS Survivor Space/ _fn: average_value

PS (MB)

  • MemoryPool/Heap/PS Gen/Committed _fn: average_value
  • MemoryPool/Heap/PS Gen/Max _fn: average_value
  • MemoryPool/Heap/PS Gen/ _fn: average_value

()

  • MemoryPool/Non-Heap/Code Cache/ _fn: average_value
  • MemoryPool/Non-Heap/PS Perm Gen/ _fn: average_value

  • GC/PS Scavenge _fn: average_call_time

  • JmxBuiltIn// _fn: average_value
  • JmxBuiltIn// _fn: average_value

? , .

+2

More articles:


All Articles