We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
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
I submitted djkoloski/rust_serialization_benchmark#56 and found that the performance of cbor4ii on github actions is worse than serde_cbor.
cbor4ii
serde_cbor
I also observed that cbor4ii has a greater slowdown than serde_cbor when using cranelift backend. (10x)
I suspect this is because cbor4ii relies more on inline than other implementations. This is a case that can be optimized.
The text was updated successfully, but these errors were encountered:
Right now we are the fastest CBOR crate for serialization, but deserialization has no advantage over serde_cbor.
Sorry, something went wrong.
No branches or pull requests
I submitted djkoloski/rust_serialization_benchmark#56 and found that the performance ofcbor4ii
on github actions is worse thanserde_cbor
.I also observed that
cbor4ii
has a greater slowdown thanserde_cbor
when using cranelift backend. (10x)I suspect this is because
cbor4ii
relies more on inline than other implementations. This is a case that can be optimized.The text was updated successfully, but these errors were encountered: