4 ms·
We were serialising/deserialising a large c++ class that consumes about 100 megabytes of memory. The reason we chose protobuf over capnproto was not performanc
by commandersaki 3y ago
We were serialising/deserialising a large c++ class that consumes about 100 megabytes of memory.
The reason we chose protobuf over capnproto was not performance but because it was already being used in other projects.
However I implemented both and didn't really do a deep comparison of performance. Basically protobuf serialisation/deserialisation was a few seconds fast. However, I didn't use capnproto as intended, in that I deserialised from the capnproto objects into an actual object which involved copying; I don't really see using the native format directly all that useful in most applications, but maybe I'm missing the point.