Fix merged to master.
Guys, thanks for the help!
В Вт, 02/07/2019 в 18:25 +0300, Alexey Goncharuk пишет:
> Hello Nikolay,
>
> I will take a look shortly.
>
> вт, 2 июл. 2019 г. в 14:30, Nikolay Izhikov :
>
> > Guys.
> >
> > I've prepared PR to fix this issue.
> > Who want to review it?
> >
Hello Nikolay,
I will take a look shortly.
вт, 2 июл. 2019 г. в 14:30, Nikolay Izhikov :
> Guys.
>
> I've prepared PR to fix this issue.
> Who want to review it?
>
> https://github.com/apache/ignite/pull/6656
>
> В Пн, 01/07/2019 в 15:17 +0300, Nikolay Izhikov пишет:
> > Hello, Igniter.
> >
> >
Guys.
I've prepared PR to fix this issue.
Who want to review it?
https://github.com/apache/ignite/pull/6656
В Пн, 01/07/2019 в 15:17 +0300, Nikolay Izhikov пишет:
> Hello, Igniter.
>
> I think we should fix the issue with slight changes in internal API (was not
> released yet).
>
> Changes
Hello, Igniter.
I think we should fix the issue with slight changes in internal API (was not
released yet).
Changes in API was independently proposed by me and Alexey Plekhanov [1]:
1. We should introduce `MetricGroup` - collection of metric of one specific
Ignite entity(io subsystem, data
Hello, Maksim.
I will take a look shortly.
В Пт, 28/06/2019 в 19:02 +0300, Maksim Stepachev пишет:
> Hello, Igniters.
>
> I see that the ticket - "[IGNITE-11848] New Monitoring. Phase1" breaks cache
> stop performance. It affects next tests: testParallelStartAndStop,
> testStartManyCaches
>
Hello, Igniters.
I see that the ticket - "[IGNITE-11848] New Monitoring. Phase1" breaks
cache stop performance. It affects next tests: testParallelStartAndStop,
testStartManyCaches
The spent time was increased 6 times:(
Look at:
