Reduce Downtime by Tuning Garbage Collection
•
0 recomendaciones•8,947 vistas
Does your JIRA sometimes freeze? Have you given Confluence more memory in an effort to speed it up? Do you think you've allocated too much or too little memory? Make users and admins happy with speedy and stable Atlassian applications. We'll go in-depth on performance tuning best practices, including the pitfalls to avoid that might make things worse. In this session, you will learn: When tuning works, and when it doesn't. How Atlassian accidentally tuned itself into more outages before diagnosing the problem and reducing outages. Best practices for performance and memory across large high impact instances. How different Java garbage collection options differ and impact performance. With the right tuning your applications will have better performance, be more stable, and scale more easily. Products covered: JIRA Software, JIRA Service Desk, Confluence
Recomendados
Recomendados
Más contenido relacionado
La actualidad más candente
La actualidad más candente (20)
Destacado
Destacado (20)
Similar a Reduce Downtime by Tuning Garbage Collection
Similar a Reduce Downtime by Tuning Garbage Collection (20)
Más de Atlassian
Más de Atlassian (20)
Último
Último (20)
Reduce Downtime by Tuning Garbage Collection
- 1. DENISE UNTERWURZACHER • CONFLUENCE ENGINEER • ATLASSIAN Trash Talk! How to Reduce Downtime by Tuning Garbage Collection
- 2. GARBAGE COLLECTION BASICS A CAUTIONARY TALE TROUBLESHOOTING Agenda TUNING BEST PRACTICES
- 3. The defaults are sane The JVM is built to react adaptively The knock-on effects can be hard to predict Don’t mess with it
- 4. EAC - extranet.atlassian.com Node 3Node 2Node 1 5.5gb VM 5.5gb VM 5.5gb VM
- 5. EAC - extranet.atlassian.com 1250 daily users
- 6. 8s
- 7. 50s
- 8. 45s
- 14. ‘Stop the world’ - stops the application running to collect garbage Collects garbage while the application runs Serial/Parallel Concurrent
- 15. Single or multi- threaded Serial/Parallel Good for small heaps ‘Stop the world’ full GCs
- 16. G1GC Needs a larger heap Still some pauses No full GCs
- 17. Young generation collections are never concurrent.
- 19. Pause types To-space allocation Full GC Young generation Mark/remark/cleanup Serial/parallel, concurrent failover All collectors Concurrent Concurrent
- 21. Benchmarking Number of pauses Length of pauses Time between pauses
- 22. <1s
- 23. Garbage collection is hard Fixes can make things worse Benchmarking is essential Lessons learned
- 25. Raw logs
- 26. Raw logs
- 27. Raw logs
- 28. Raw logs
- 29. Raw logs
- 30. Raw logs
- 31. Raw logs
- 32. Raw logs
- 33. Raw logs
- 34. Raw verbose logs
- 35. Raw verbose logs
- 36. Raw verbose logs
- 37. Raw verbose logs
- 38. Raw verbose logs
- 39. Raw verbose logs
- 40. Raw verbose logs
- 41. GC Viewer
- 48. GC Viewer < 0.10 s
- 49. GC Viewer
- 51. GC Viewer
- 52. GC Viewer
- 53. GC Viewer
- 54. GC Viewer
- 55. GC Viewer
- 56. When GC fails
- 57. OutOfMemory Error - Java Heap Space
- 58. Long pauses
- 59. Bad tuning - new generation too small
- 60. Heap too large GC times
- 61. Long pauses - allocation failure To-space allocation failure Full GC
- 62. Long pauses - unable to free enough space
- 63. Solutions Long pauses Heap too large OOMEs Increase memory by small increments. Decrease memory. Diagnose, benchmark, test.
- 64. Best Practices
- 66. Tuning Goals Footprint Throughput Latency Maximum GC pause times Time spent serving application requests The size of the heap
- 67. Footprint Throughput Pause times Low pause times + high throughput Use G1GC and a large heap
- 68. Footprint Throughput Pause times Low pause times + low footprint Use G1GC and a medium sized heap
- 69. Footprint Throughput Pause times Low pause times + low footprint Use G1GC and a medium sized heap
- 70. Footprint Throughput Pause times High throughput + low footprint Use a parallel collector and a small heap
- 71. Footprint Throughput Pause times High throughput + low footprint Use a parallel collector and a small heap
- 72. JVM auto-tuning 3. Footprint 2. Throughput 1. Latency Maximum GC pause times Time spent serving application requests The size of the heap
- 73. Overtuning Increasing the heap too much Parameters that stop the heap auto- tuning
- 74. -XX:MaxNewSize=2g -XX:NewRatio=3 Hard tuning Soft tuning Young Generation
- 75. -XX:GCTimeLimit=10 -XX:GCTimeRatio=9 Hard tuning Soft tuning -XX:MaxGCPauseMillis=500 Throughput
- 76. -XX:SurvivorRatio=4 -XX:G1ReservePercent=20 Hard tuning Soft tuning Survivor
- 77. Tuning is hard. Avoid it.
- 78. If you have to tune, tread carefully.
- 79. Have a plan.
- 81. What you can do when you get home Be minimal! Think about goals Review current state
- 82. Where to get help with GC Atlassian Support Oracle’s docs Atlassian’s docs https://confluence.atlassian.com/x/ aACCGw http://tinyurl.com/caq6y7h https://support.atlassian.com
- 83. Thank you! DENISE UNTERWURZACHER • CONFLUENCE ENGINEER • ATLASSIAN