You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@ignite.apache.org by "Nikolay Izhikov (Jira)" <ji...@apache.org> on 2019/09/24 07:12:00 UTC

[jira] [Updated] (IGNITE-11912) [IEP-35] Research possibility to optimize MetricRegistry

     [ https://issues.apache.org/jira/browse/IGNITE-11912?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Nikolay Izhikov updated IGNITE-11912:
-------------------------------------
    Fix Version/s: 2.8

> [IEP-35] Research possibility to optimize MetricRegistry
> --------------------------------------------------------
>
>                 Key: IGNITE-11912
>                 URL: https://issues.apache.org/jira/browse/IGNITE-11912
>             Project: Ignite
>          Issue Type: Improvement
>            Reporter: Nikolay Izhikov
>            Assignee: Nikolay Izhikov
>            Priority: Major
>              Labels: IEP-35
>             Fix For: 2.8
>
>
> We should research and benchmark different data structure for a MetricRegistry implementation.
> A basic assumption of `MetricRegistry` usage:
> 1. Collection of metrics almost constant during Ignite lifetime. It will be changed on cache creation(destroy) and other not frequent operations.
> 2. Collection of metrics will be read very frequently(each several seconds or frequently) by configured metric exporters.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)