Skip to end of banner
Go to start of banner

Spike: Investigate high memory usage

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 6 Next »

Requirements:  MODINVOICE-101 - Getting issue details... STATUS MODORDERS-311 - Getting issue details... STATUS MODORGS-45 - Getting issue details... STATUS

Memory issues detection approach

Throttled mode of service load is most convenient way to identify memory leaks or another memory utilization issues. The utility https://github.com/khandramai/gatling-folio-performance for emulation of load regime was implemented based on load and performance testing framework Gatling.

In scope of this investigation cyclic CRUD operations in 25 threads during 4 hours was used as base load. Monitoring of service operating was carried out with using the VisualVM profiler.

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

Heap dumps: mod-invoices.hprofmod-invoices-storage.hprof

Summary

TBD

  • No labels