[DISCUSSION] Moving tracing feature to GA

classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

[DISCUSSION] Moving tracing feature to GA

Valentin Kulichenko
Igniters,

As far as I know, the tracing feature [1] is still marked as experimental.
However, It seems that we've had it for a while, it's being used, the API
is stabilized, and there are no known performance issues associated with it.

That said, should we remove the "experimental" mark and move the feature to
the GA status? Please share your thoughts.

[1] https://ignite.apache.org/docs/latest/monitoring-metrics/tracing

-Val
Reply | Threaded
Open this post in threaded view
|

Re: [DISCUSSION] Moving tracing feature to GA

Nikolay Izhikov-2
Hello, Valentin.

I’m -1 to make Tracing API GA

>  the API is stabilized, and there are no known performance issues associated with it.

For now, API works with strings only and this leads to huge performance degradation when tracing enabled.
Our measurement shows about 50% drop.

Moreover, as we discussed earlier, there is a plan to merge internals of tracing and performance profiling
To make it, we should enhance Tracing API and learn it to work with primitives in some king of lazy manner.

So, I think we can’t stabilise Tracing API, for now.

You can find more details in meetup talk (in Russian) [1]

[1] https://www.youtube.com/watch?v=68QoOBD574g


> 13 февр. 2021 г., в 04:23, Valentin Kulichenko <[hidden email]> написал(а):
>
> Igniters,
>
> As far as I know, the tracing feature [1] is still marked as experimental.
> However, It seems that we've had it for a while, it's being used, the API
> is stabilized, and there are no known performance issues associated with it.
>
> That said, should we remove the "experimental" mark and move the feature to
> the GA status? Please share your thoughts.
>
> [1] https://ignite.apache.org/docs/latest/monitoring-metrics/tracing
>
> -Val