ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Nikolay Izhikov (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (IGNITE-11927) [IEP-35] Add ability to enable\disable subset of metrics
Date Thu, 18 Jul 2019 13:01:00 GMT

    [ https://issues.apache.org/jira/browse/IGNITE-11927?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16887958#comment-16887958

Nikolay Izhikov commented on IGNITE-11927:


Sorry, I still don't understand you.
Can you, please, make a simple, pseudo-code example of your idea?

> Motivation: reducing memory consuming and GC pressure. There are users with big amount
of caches (I saw cases with 5000 caches in 200 cache groups).

We can have NoOp implementation of MetricRegistries disabled in the config file. And this
registries never can be enabled.

But this motivation looks very odd for me:
1. If we have 5000 caches, Ignite structures already huge. Why do you think metrics bring
a huge impact on GC?

2. All {AtomicLong} fields are created in previous versions of CacheMetricsImpl. MetricRegistry
is the only addition we made with the new framework.

Do we have some benchmarks or other descriptions of this issue?

> [IEP-35] Add ability to enable\disable subset of metrics
> --------------------------------------------------------
>                 Key: IGNITE-11927
>                 URL: https://issues.apache.org/jira/browse/IGNITE-11927
>             Project: Ignite
>          Issue Type: Improvement
>            Reporter: Nikolay Izhikov
>            Assignee: Nikolay Izhikov
>            Priority: Major
>              Labels: IEP-35
>          Time Spent: 10m
>  Remaining Estimate: 0h
> Ignite should be able to:
> * Enable or disable an arbitrary subset of the metrics. User should be able to do it
in runtime.

This message was sent by Atlassian JIRA

View raw message