-
Notifications
You must be signed in to change notification settings - Fork 16
Add more performant manual recorder #231
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
Conversation
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.
The changes look good. I'm wondering how users will follow all the options available in this code. For example, is there any document that describes all the recorder options?
include/lightstep/buffer_chain.h
Outdated
|
||
namespace lightstep { | ||
/** | ||
* BufferChain provides an interface to access a chained sequestion of |
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.
nit: sequestration?
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.
Fixed
You can't set recorder options directly, but there's documentation for all the tracer options. https://github.com/rnburn/lightstep-tracer-cpp/blob/manual-v2/include/lightstep/tracer.h#L52 I mostly wanted to keep the LegacyManualTransporter around so that we have an easy way to benchmark the two approaches for building up the report request protobuf message |
Add a replacement for the existing manual tracer that provides better performance.
In benchmarking, it has around a 2x-5x improvement