Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Benchmarks for Binary formats #733

Closed
D1amond opened this issue Sep 8, 2017 · 4 comments
Closed

Benchmarks for Binary formats #733

D1amond opened this issue Sep 8, 2017 · 4 comments
Labels
aspect: binary formats BSON, CBOR, MessagePack, UBJSON kind: enhancement/improvement state: stale the issue has not been updated in a while and will be closed automatically soon unless it is updated

Comments

@D1amond
Copy link

D1amond commented Sep 8, 2017

It would be nice to have an idea of the parsing time difference between a JSON file and a binary serialized version of the same file.

This could be included in the library's benchmarks.
@stale
Copy link

stale bot commented Oct 25, 2017

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the state: stale the issue has not been updated in a while and will be closed automatically soon unless it is updated label Oct 25, 2017
@hackboxlive
Copy link

I am new to the library, but I would definitely like to work on this issue. Could you point me into some right direction?

@stale stale bot removed the state: stale the issue has not been updated in a while and will be closed automatically soon unless it is updated label Oct 26, 2017
@nlohmann
Copy link
Owner

@hackboxlive We would need some benchmark code (in addition to https://github.com/nlohmann/json/tree/develop/benchmarks) that compares the parsing time for various JSON files compared to their CBOR/MessagePack versions.

@stale
Copy link

stale bot commented Nov 26, 2017

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the state: stale the issue has not been updated in a while and will be closed automatically soon unless it is updated label Nov 26, 2017
@stale stale bot closed this as completed Dec 3, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
aspect: binary formats BSON, CBOR, MessagePack, UBJSON kind: enhancement/improvement state: stale the issue has not been updated in a while and will be closed automatically soon unless it is updated
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@nlohmann @D1amond @hackboxlive