...

The Ignite will log some additional internal performance statistics to profiling files (IgniteProfiling interface). The format is like WAL logging.

One disk-writer thread and off-heap memory buffer will be used to minimize affect on performance. Maximum file size and buffer size can be configured on start.

The new ignite-profiling module extension performance-statistics-ext module will be introduced. It will contain the tool to build the report: profiling build-report.sh(bat). The JSON format is used to store aggregated statistics and next draw in the report.

The report is based on the bootstrap library and can be viewed in a browser offline.

...

Management

1) JMX:

...

PerformanceStatisticsMBean

void startProfiling(long maxFileSize, int bufferSize, int flushBatchSizestart() // Start profiling Start collecting performance statistics in the cluster with custom parameters.
void stopProfilingstop() // Stop profiling Stop collecting performance statistics in the cluster.
boolean profilingEnabledenabled() // True if profiling collecting performance statistics enabled.

2) Control.sh utility. Functionality is like JMX.

Public API changes

The new module will be created: ignite-profiling.

The script to build the report: profiling.sh(bat)

...

3) System properties:

IGNITE_PERF_STAT_FILE_MAX_SIZE - Performance statistics maximum file size in bytes. Performance statistics will be stopped when the size exceeded.
IGNITE_PERF_STAT_BUFFER_SIZE - Performance statistics offheap buffer size in bytes.
IGNITE_PERF_STAT_FLUSH_SIZE - Performance statistics minimal batch size to flush in bytes.
IGNITE_PERF_STAT_CACHED_STRINGS_THRESHOLD - Performance statistics maximum cached strings threshold. String caching will stop on threshold excess.