Add a benchmark for endoding/decoding about proto-lens HOT 4 CLOSED

I am working on a set of criterion benchmarks.

from proto-lens.

Some updates... adding criterion benchmarks was quite simple. So I'm currently trying to figure out what a reasonable initial set of benchmarks looks like. The only thing remotely like a "standard benchmark" I could find was here: https://github.com/google/protobuf/tree/master/benchmarks. But I'm not sure we benefit much from imitating it; it looks like a raw speed test for a single large, heterogeneous proto. It seems more interesting to me to have a larger number of small, focused test cases to help uncover pathological cases (at least right now, with our largely unoptimized code).

So for the initial PR I guess I'll just come up with a small set of test cases that make sense to me. If anyone disagrees with the above or has any requests for specific benchmarks, please respond here. :)

from proto-lens.

That plan sounds great; thanks for taking this on!

Eventually we should test the effect of proto-lens putting all fields in a single, immutable, flat Haskell record. For large protos my guess is it's significantly less efficient (in particular, for decoding) than languages which can do updates by mutating a single field. The standard benchmark might help us examine that use case.

from proto-lens.

Closing since the current set of benchmarks has proven useful so far. If we run into any particular bottlenecks in the future, we can add more specific benchmarks as needed.

from proto-lens.