FlatBuffers

[rw]

Cool project! Could I suggest that you try to incorporate the new FlatBuffers Rust port that just landed? google/flatbuffers@3c54fd9

[jeikabu]

@rw
I didn't see this, but I made an attempt to add FlatBuffers: #4

The results seem a bit... off. I'm not entirely sure about the differences between what FlatBuffers and the rest are doing, so it's likely comparing apples to... a different kind of apple.

I used 1.10 instead of HEAD.

[rw]

@jeikabu Your complex_build seems to be causing heap allocations.

1. Re-use the builder by calling .reset() on it to re-use the memory. This is very important to do in tight loops, like in benchmarks.
2. Don't use .to_vec in builder.finished_data().to_vec(), because that causes an alloc.
3. HEAD might be better but I don't think you're using any functionality that has landed since 1.10.
4. Thanks for doing this! :-)

[jake-ruyi]

1. Ok
2. to_vec() was actually intentional because both capn and protobuf are generating a Vec<_>, but I'll go ahead and remove it. I suspect the other two need to be updated anyway.
3. Release 1.11! ;)

[jeikabu]

After looking at it again re-creating the builder was also intentional as the capnp bench does the same thing. Hardly seems fair to move it out without doing it to the others. Switching new() for new_with_capacity() was a big win, though.

[rw]

@jeikabu I think if you don't re-use Builders, then you're basically benchmarking Rust's heap allocator... not flatbuffers :-)