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.

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

Start using FlatBuffers instead of Google Protobuf #15

Open
kornilova203 opened this issue Jun 8, 2018 · 2 comments
Open

Start using FlatBuffers instead of Google Protobuf #15

kornilova203 opened this issue Jun 8, 2018 · 2 comments

Comments

@kornilova203
Copy link
Owner

Start using Cap'n Proto instead of Google Protobuf for client-server communications. This will speed up visualization and reduce memory consumption.

@kornilova203
Copy link
Owner Author

I could not find supported stable cap'n proto library for browser javascript:
Here are all options I could find:

Next option to check is FlatBuffers

@kornilova203
Copy link
Owner Author

FlatBuffers is much faster.
It takes ~800ms to create and serialize a tree with 524288 nodes with flatbuffers, and ~3s with protobuf.
Although resulting file is bigger 50Mb vs 20Mb. But disk space should not be a problem and serialization/deserialization time is much more important.
Also FlatBuffers should reduce runtime memory consumption.

@kornilova203 kornilova203 changed the title Start using Cap'n Proto instead of Google Protobuf Start using FlatBuffers instead of Google Protobuf Jul 15, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant