Consecutive Full GC
Our analysis tells that Full GCs are consecutively running in your application. It might cause intermittent OutOfMemoryErrors or degradation in response time or high CPU consumption or even make application unresponsive.
Read our recommendations to resolve consecutive Full GCs
Poor Throughput
Our analysis tells that your application is spending too much time on GC. 10.68% of time is spent on GC. Too much GC activity degrades response time + consumes CPU. It's ideal to keep GC time under 5%.Read our recommendations to increase throughput
JVM Heap Size
| Generation | Allocated | Peak |
|---|---|---|
| Young Generation | 10.38 gb | 9.59 gb |
| Old Generation | 5.62 gb | 8.31 gb |
| Total | 16 gb | 14.1 gb |
Key Performance Indicators
(Important section of the report. To learn more about KPIs, click here)
1 Throughput : 89.325%
2 Latency:
| Avg Pause GC Time | 315 ms |
|---|---|
| Max Pause GC Time | 1 sec 290 ms |
GC Pause Duration Time Range :
| Duration (secs) | No. of GCs | Percentage |
|---|---|---|
| 0 - 1 | 3834 | 99.9% |
| 1 - 2 | 4 | 0.1% |
Interactive Graphs
(All graphs are zoomable)
G1 Collection Phases Statistics
| Young GC | Concurrent Mark | Mixed | initial-mark | Cleanup | Remark | Total | |
|---|---|---|---|---|---|---|---|
| Count | 2750 | 199 | 496 | 199 | 199 | 199 | 4042 |
| Total GC Time | 15 min 21 sec 140 ms | 8 min 47 sec 146 ms | 3 min 27 sec 760 ms | 1 min 5 sec 90 ms | 9 sec 470 ms | 5 sec 800 ms | 28 min 56 sec 406 ms |
| Avg GC Time | 335 ms | 2 sec 649 ms | 419 ms | 327 ms | 48 ms | 29 ms | 430 ms |
| Avg Time std dev | 120 ms | 1 sec 107 ms | 179 ms | 86 ms | 30 ms | 29 ms | 582 ms |
| Min/Max Time | 0 / 840 ms | 0 / 5 sec 299 ms | 0 / 1 sec 290 ms | 0 / 660 ms | 0 / 200 ms | 0 / 200 ms | 0 / 5 sec 299 ms |
| Avg Interval Time | 4 sec 120 ms | 37 sec 410 ms | 12 sec 24 ms | 37 sec 402 ms | 37 sec 410 ms | 37 sec 410 ms | 11 sec 622 ms |
G1 GC Time
Pause Time
| Total Time | 20 min 9 sec 262 ms |
|---|---|
| Avg Time | 315 ms |
| Std Dev Time | 156 ms |
| Min Time | 0 |
| Max Time | 1 sec 290 ms |
Concurrent Time
| Total Time | 8 min 47 sec 146 ms |
|---|---|
| Avg Time | 2 sec 649 ms |
| Std Dev Time | 1 sec 107 ms |
| Min Time | 0 |
| Max Time | 5 sec 299 ms |
Object Stats
(These are perfect micro-metrics to include in your performance reports)
| Total created bytes | 21.63 tb |
|---|---|
| Total promoted bytes | 805.85 gb |
| Avg creation rate | 1.95 gb/sec |
| Avg promotion rate | 72.85 mb/sec |
Memory Leak
No major memory leaks.
(Note: there are 8 flavours of OutOfMemoryErrors. With GC Logs you can diagnose only 5 flavours of them(Java heap space, GC overhead limit exceeded, Requested array size exceeds VM limit, Permgen space, Metaspace). So in other words, your application could be still suffering from memory leaks, but need other tools to diagnose them, not just GC Logs.)
Long Pause
None.
Safe Point Duration
(To learn more about SafePoint duration, click here)
| Total Time | Avg Time | % of total duration | |
|---|---|---|---|
| Total time for which app threads were stopped | 1215.136 secs | 0.154 secs | 10.728 % |
| Time taken to stop app threads | 3.37 secs | 0.0 secs | 0.03 % |
GC Causes
(What events caused the GCs, how much time it consumed?)
| Cause | Count | Avg Time | Max Time | Total Time | Time % |
|---|---|---|---|---|---|
| G1 Evacuation Pause | 3425 | 347 ms | 1 sec 287 ms | 19 min 48 sec 786 ms | 68.46% |
| Others | 597 | n/a | n/a | 9 min 2 sec 279 ms | 31.23% |
| G1 Humongous Allocation | 16 | 328 ms | 519 ms | 5 sec 243 ms | 0.3% |
| Metadata GC Threshold | 4 | 26 ms | 53 ms | 103 ms | 0.01% |
| Total | 4042 | n/a | n/a | 28 min 56 sec 410 ms | 100.0% |
Tenuring Summary
Desired Survivor Size: 616.0 mb,
Max Threshold: 15
| Age | Survival Count | Average size (kb) | Average Total 'To' size (kb) |
|---|---|---|---|
| age 1 | 3444 | 283534.12 | 283534.12 |
| age 2 | 3032 | 251474.25 | 549794.42 |
| age 3 | 900 | 79078.2 | 517896.06 |
| age 4 | 464 | 14118.97 | 475802.31 |
| age 5 | 295 | 5940.15 | 342356.93 |
| age 6 | 234 | 2226.68 | 216732.85 |
| age 7 | 230 | 2150.72 | 211236.1 |
| age 8 | 228 | 2156.57 | 211823.44 |
| age 9 | 226 | 2162.35 | 212369.18 |
| age 10 | 224 | 2163.39 | 213028.44 |
| age 11 | 222 | 2167.2 | 213766.61 |
| age 12 | 220 | 2176.35 | 214593.17 |
| age 13 | 218 | 2184.56 | 214480.25 |
| age 14 | 217 | 2187.63 | 216402.16 |
| age 15 | 216 | 2190.54 | 218320.03 |
Command Line Flags
-XX:+AlwaysPreTouch -XX:CompileCommandFile=/etc/dse/cassandra/hotspot_compiler -XX:ErrorFile=/var/lib/cassandra/hs_err_1543415642.log -XX:G1RSetUpdatingPauseTimePercent=5 -XX:GCLogFileSize=10485760 -XX:+HeapDumpOnOutOfMemoryError -XX:HeapDumpPath=/var/lib/cassandra/java_1543415642.hprof -XX:InitialHeapSize=17179869184 -XX:+ManagementServer -XX:MaxDirectMemorySize=25301090304 -XX:MaxGCPauseMillis=2000 -XX:MaxHeapSize=17179869184 -XX:NumberOfGCLogFiles=10 -XX:+PerfDisableSharedMem -XX:+PreserveFramePointer -XX:PrintFLSStatistics=1 -XX:+PrintGC -XX:+PrintGCApplicationStoppedTime -XX:+PrintGCDateStamps -XX:+PrintGCDetails -XX:+PrintGCTimeStamps -XX:+PrintHeapAtGC -XX:+PrintPromotionFailure -XX:+PrintTenuringDistribution -XX:+ResizeTLAB -XX:-RestrictContended -XX:StringTableSize=1000003 -XX:ThreadPriorityPolicy=42 -XX:ThreadStackSize=256 -XX:+UnlockDiagnosticVMOptions -XX:+UseCompressedClassPointers -XX:+UseCompressedOops -XX:+UseG1GC -XX:+UseGCLogFileRotation -XX:+UseTLAB -XX:+UseThreadPriorities
Become a DevOps champion in your organization
(Best practises/tools)
- Use fastThread.io tool to analyze thread dumps, core dumps and hs_err_pid files
- Do proactive Garbage Collection analysis on all your JVMs (not just one or two) using the GC log analysis API
- Always rotate the GC log files to prevent critical garbage collection data loss
- Use 'Enterprise' edition for 10x fast, unlimited, secure usage
Do you like this report?
Please share your feedback. |
|||||
|
|
|||||
Thanks for your valuable Feedback!Your comment has been posted in the User Reviews page. |
|||||