-
Notifications
You must be signed in to change notification settings - Fork 99
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
send batches concurrently in each flush and compress payload #720
Conversation
@@ -1,6 +1,8 @@ | |||
package data | |||
|
|||
import ( | |||
"bytes" | |||
"compress/gzip" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this will be fine for now, but we will need to look at adopting lz4 compression to help improve performance.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
idk if there's choice for now as the OTLP doc is quite confusing, specification here says it only need to support gzip
to meet the minimal requirement for a OTLP server
atomic.AddUint64(&bd.seriesSent, uint64(b.lenMetrics())) | ||
} | ||
func(g group) { | ||
eg.Go(func() error { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Cool this means async sends? Do we have any retries in the otlp backend?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yeah retry is in the postMetrics
Send batches concurrently in each flush and compress payload.
This should shorten process time for each flush and also reduce the size of payload.