3 ms·
Project contributor here :) We want to continuously try with different micro optimizations or even architecture changes that can help us achieve the best perfor
by breezewish 5y ago
Project contributor here :) We want to continuously try with different micro optimizations or even architecture changes that can help us achieve the best performance that we want. Some optimizations result in trace offs in public interfaces or features that are not compatible with the common interface or even the opentracing standard. Therefore, we chose to build our own library. We think users will find it useful when full-features can be sacrificed for better performance. However some optimizations mentioned in this article can be made available in the `tracing` library easily, for example, the timing optimization has been extracted to `minstant` and can be just adopted. We are glad to help if the community is interested!
- staticassertion 5y agoGot it. Yeah it might be worthwhile to see what you can push without having to worry about the same constraints, though keeping an open channel so that they can find their way into the tracing library would certainly be helpful. I'm not a tracing contributor myself, just a consumer, for what it's worth.