Speed test loading the different formats cbor, msgpack, bson, json #2581
phforesteot
started this conversation in
General
Replies: 4 comments 2 replies
-
|
Just to make sure:
|
Beta Was this translation helpful? Give feedback.
1 reply
-
|
I've used the two different version a old one and the one from 2 days ago. Both had similar results. Note: I've also added ubjson and I had similar results as msgpack and cbor. |
Beta Was this translation helpful? Give feedback.
-
|
Hi, I ran the benchmark, and got the following results: json size:9237533 ubjson size:8254249 msgpack size:6262275 cbor size:6256853 bson size:16846041 which confirm @phforesteot 's report. |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
Here are my results using Google Benchmark: I am also surprised by the results, but I have not yet found the time to look into the code to understand the reason why the binary formats are slower. |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
Very interesting discussion. Did anyone test the latest versions? I wonder if the slowness of binary formatting has been addressed |
Beta Was this translation helpful? Give feedback.
1 reply
-
|
aI just did a quick test with an extended version of https://github.com/nlohmann/json/blob/788e5468e4cb4573941600d5c39ccd552dc8a429/tests/benchmarks/src/benchmarks.cpp serialization seems to be a bit faster than (compact) json dumps (ToMsgpack vs Dump / ... / -), whereas deserialization tends to be slower for larger documents but faster for the individual number tests (FromMsgpack vs ParseString). for reference, the added benchmark code: static void ToMsgpack(benchmark::State& state, const char* filename)
{
std::ifstream f(filename);
std::string str((std::istreambuf_iterator<char>(f)), std::istreambuf_iterator<char>());
json j = json::parse(str);
for (auto _ : state)
{
json::to_msgpack(j);
}
state.SetBytesProcessed(state.iterations() * json::to_msgpack(j).size());
}
BENCHMARK_CAPTURE(ToMsgpack, jeopardy, TEST_DATA_DIRECTORY "/jeopardy/jeopardy.json");
BENCHMARK_CAPTURE(ToMsgpack, canada, TEST_DATA_DIRECTORY "/nativejson-benchmark/canada.json");
BENCHMARK_CAPTURE(ToMsgpack, citm_catalog, TEST_DATA_DIRECTORY "/nativejson-benchmark/citm_catalog.json");
BENCHMARK_CAPTURE(ToMsgpack, twitter, TEST_DATA_DIRECTORY "/nativejson-benchmark/twitter.json");
BENCHMARK_CAPTURE(ToMsgpack, floats, TEST_DATA_DIRECTORY "/regression/floats.json");
BENCHMARK_CAPTURE(ToMsgpack, signed_ints, TEST_DATA_DIRECTORY "/regression/signed_ints.json");
BENCHMARK_CAPTURE(ToMsgpack, unsigned_ints, TEST_DATA_DIRECTORY "/regression/unsigned_ints.json");
BENCHMARK_CAPTURE(ToMsgpack, small_signed_ints, TEST_DATA_DIRECTORY "/regression/small_signed_ints.json");
static void FromMsgpack(benchmark::State& state, const char* filename)
{
std::ifstream f(filename);
std::string str((std::istreambuf_iterator<char>(f)), std::istreambuf_iterator<char>());
auto bytes = json::to_msgpack(json::parse(str));
for (auto _ : state)
{
state.PauseTiming();
auto* j = new json();
state.ResumeTiming();
*j = json::from_msgpack(bytes);
state.PauseTiming();
delete j;
state.ResumeTiming();
}
state.SetBytesProcessed(state.iterations() * bytes.size());
}
BENCHMARK_CAPTURE(FromMsgpack, jeopardy, TEST_DATA_DIRECTORY "/jeopardy/jeopardy.json");
BENCHMARK_CAPTURE(FromMsgpack, canada, TEST_DATA_DIRECTORY "/nativejson-benchmark/canada.json");
BENCHMARK_CAPTURE(FromMsgpack, citm_catalog, TEST_DATA_DIRECTORY "/nativejson-benchmark/citm_catalog.json");
BENCHMARK_CAPTURE(FromMsgpack, twitter, TEST_DATA_DIRECTORY "/nativejson-benchmark/twitter.json");
BENCHMARK_CAPTURE(FromMsgpack, floats, TEST_DATA_DIRECTORY "/regression/floats.json");
BENCHMARK_CAPTURE(FromMsgpack, signed_ints, TEST_DATA_DIRECTORY "/regression/signed_ints.json");
BENCHMARK_CAPTURE(FromMsgpack, unsigned_ints, TEST_DATA_DIRECTORY "/regression/unsigned_ints.json");
BENCHMARK_CAPTURE(FromMsgpack, small_signed_ints, TEST_DATA_DIRECTORY "/regression/small_signed_ints.json"); |
Beta Was this translation helpful? Give feedback.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hi,
I was trying to figure out which format to use to gain speed and size. I was assuming that one of the binary format would be faster and smaller, but much to my surprise.
json: using parse(...)
msgpack: using from_msgpack( ... )
cbor: using from_cbor( ... )
bson: using from_bson( ... )
-size: 16846041
My conclusion was:
json is still way much faster that any binary format's (which i do not understand way) we are talking something 50%.
msgpack, cbor have the best sizes.
According to the msgpack and cbor they should also be faster !
My test environment to test this.
https://github.com/phforesteot/json_speed_test
Any help is welcome.
Thanks.
Great library by the way.
Beta Was this translation helpful? Give feedback.
All reactions