-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
proto: specialize map<string, string> for performance #781
Labels
Comments
fwiw, I wrote a quick benchmark for comparing against gogo faster:
Top is |
If nobody is working on this I would like to get assigned to this. |
Making a note that this should probably also handle |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Background: #624
Serialization of map fields currently hits a slow, reflection-based path. This is understandable for the general case (nested messages are hard), but there are some special cases where maps get used a lot and a fast path would be very valuable.
My specific use case is a
map<string, string>
used to represent arbitrary human-meaningful metadata in a distributed monitoring system (similar to Prometheus). Benchmarking shows that our tooling is spending a material amount of CPU time in the closures returned fromproto.makeMapMarshaler
.The text was updated successfully, but these errors were encountered: