You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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? ;)
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.
I know FST makes objects take up less space, but how does it handle the extra overhead? Such as the loss of time complexity?
The text was updated successfully, but these errors were encountered: