News for hackers. Stuff that matters.
Re:Fury: 170x faster than JDK, blazing fast serialization by... by gigatexal on Sunday October 08, 2023 @01:46PM (#37812696)
can someone help a noob like me understand where i would use something like this? is this a way to get faster json parsing?
Re:Fury: 170x faster than JDK, blazing fast serialization by... by chaokunyang on Sunday October 08, 2023 @11:07PM (#37816529)
Json doesn't support polymorphism and circular/shared references, those scenarios are more suitable for fury. And json is a text protocol, which is inefficient compared to fury binary protocol. Taking jackson json lib as an example: 1) Fury is 41.6x faster than jackson for Struct serialization 2) Fury is 65.6x faster than jackson for Struct deserialization 3) Fury is 9.4x faster than jackson for MediaContent serialization 4) Fury is 9.6x faster than jackson for MediaContent deserialization

For http rest api, json is more suitable. For RPC/bigdata/game/scheduling, fury may be better

Re:Fury: 170x faster than JDK, blazing fast serialization by... by gigatexal on Monday October 09, 2023 @02:04AM (#37817352)
Thank you chao!
Re:Fury: 170x faster than JDK, blazing fast serialization by... by chaokunyang on Monday October 09, 2023 @02:09AM (#37817391)
Another issue for json format is that it will bloat the payload. For example, for an int `1111122222` will take 10 bytes in json, but only 4 bytes in fury. `0.3333333333333333` will need 18 bytes in json, but only 4 bytes in fury.