Details
-
Improvement
-
Status: Open
-
Major
-
Resolution: Unresolved
-
2.0.3-alpha, 0.23.6, 3.0.0-alpha1
-
None
-
None
-
None
Description
The default is to optimize for code size : https://groups.google.com/forum/?fromgroups=#!topic/protobuf/OtL7Bb4NiRI
Has anyone ever investigated how much effort protobuf de/serialization takes and whether it would make a difference if we used this option? In benchmarks, the options seems to make a huge difference:
http://www.eishay.com/2008/11/protobuf-with-option-optimize-for-speed.html
http://code.google.com/p/thrift-protobuf-compare/wiki/Benchmarking
I don't plan to take this up, so if anybody else does, please feel free