Skip to content
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

Use TBinaryProtocolAccelerated when serializing reports. #90

Closed

Conversation

rowillia
Copy link

We're currently seeing our services spend a large amount of time inside of the lightstep sdk
serializing reports when they instrument themselves with tracing. This is in large part due to
the fact that lightstep is using the pure python implemenation of Thrift.

Fixes #89

We're currently seeing our services spend a large amount of time inside of the lightstep sdk
serializing reports when they instrument themselves with tracing.  This is in large part due to
the fact that lightstep is using the pure python implemenation of Thrift.

Fixes lightstep#89
Alex Boten added 4 commits January 17, 2020 14:47
When using THttpClient.THttpClient as the transport, an invalid status code could cause memory usage to spike. This behaviour is corrected via TTransport.TBufferedTransport, so this check is no longer needed.

Signed-off-by: Alex Boten <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Lightstep appears to be using pure python thrift code
2 participants