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

Why FST is faster than JDK #326

Open
wellCh4n opened this issue Jun 22, 2022 · 2 comments
Open

Why FST is faster than JDK #326

wellCh4n opened this issue Jun 22, 2022 · 2 comments

Comments

@wellCh4n
Copy link

I know FST makes objects take up less space, but how does it handle the extra overhead? Such as the loss of time complexity?

@chrisco484
Copy link

chrisco484 commented Aug 18, 2022

What is the extra overhead? It stores Java objects much more concisely that the JDK does - much less overhead with each object because it doesn't repeat entire package/class names.

Not sure what you mean by the 'loss of time complexity'? Did you discover the fast-serialization's secret flux capacitor? ;)

@wellCh4n
Copy link
Author

What is the extra overhead? It stores Java objects much more concisely that the JDK does - much less overhead with each object because it doesn't repeat entire package/class names.

Not sure what you mean by the 'loss of time complexity'? Did you discover fast-serialization's secret flux capacitor? ;)

@chrisco484 Thanks for your reply~
I thought FST was using scalable object length a few days ago, there would be extra overhead to restore it to JDK format, but I learned from your answer that it is actually achieved by reducing the length of class name. Thank you very much.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants