...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
Requirements:
| Jira Legacy | |
|---|---|
|
...
|
...
|
...
|
...
|
...
|
...
|
| Jira Legacy | |
|---|---|
|
...
|
...
|
...
|
...
|
...
|
...
|
| Jira Legacy | |
|---|---|
|
...
|
...
|
...
|
...
|
...
|
...
|
Memory issues detection approach
...
Deep analysis of the memory utilization was performed with using Eclipse Memory Analyzer on the basis of memory dumps prepared in advance during the operation of the service (after 1 hour of service operating).
Founded issues
JMX reporting based on Dropwizard metrics
Description
TBD
Detailed investigation
Emulation of the load on local equipment showed the following results.
CPU/Heap utilization:
Heap dumps: mod-invoices.hprof, mod-invoices-storage.hprof.
Heap dumps analysis showed that problem relates to drop wizard metrics collecting. After manual disabling of metrics collecting load test passes successfully with the following CPU/Heap utilization during 4 hours:
mod-invoice
mod-invoice-storage
Heap dumps analysis showed that issue was fixed.
Summary
Disable Dropwizard metrics on production environment.