Prabhakar Sithanandam
Prabhakar Sithanandam
+1 on @gashutos point. @rishabhmaurya - Do you have a specific use case where this will be useful?
@Bukhtawar - Thanks for the proposal. Format could mean two things here, i) format of the data represented as part of the document, ii) format of the data in rest...
@VachaShah - 100th percentile is generally skewed, 90th percentile is more reliable, can you please share the numbers for 90th and 99th percentile. Also, are these single runs or average...
@ansjcy - Do you think ```G1UsePreventiveGC``` is the root cause or it is something else? @tophercullen - Can you please share the heap dumps? @dblock - Is there a common...
+1, I like the idea of migrating the Performance Analyzer plugin metrics into the OpenTelemetry format. But, would like to understand bit more on deprecation of "Performance Analyzer" plugin part....
> The tail base sampling would be done outside of OpenSearch (on Otel exporter side), so we should be not concerned too much by additional computation and memory I believe...
>... keeping the traces state of tens of thousands of the requests on OpenSearch side in case any of them may backfire is unsound design decision from the start (at...
> Yes, but in most of the cases parent span ends post child is ended (except some async scenarios). Thanks! exactly the point.
Tagging @sarthakaggarwal97 to take a look.
Thanks @sarthakaggarwal97 for the detailed analysis. While Zstandard is a good fit for this use case (duplicate values), what are your thoughts on exposing block size as a configurable parameter?