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 your use-case and why do you need this feature?
I need to serialize objects with many Doubles in them. The JDK's default Double serialization is slow, particularly on Android phones.
I can use custom serializers of course, but I would rather have a fast default implementation.
Describe the solution you'd like
Use Daniel Lemire's fast_float algorithm for parsing Double instead of the JDK's default. The speedup is considerable, almost 4x on Android for my quick checks.
Is it a drop-in replacement though? We can't swap one implementation for another unless it always gives the same result, and IIRC, java.lang.Double.valueOf support various input formats, such as hexadecimal.
I think the most impactful thing would be to adopt it in the downstream toolchain itself instead.
The problem with changing such an intricate thing as Java's Double parser is that it might introduce quite subtle inconsistencies across the systems; also, for the sake of some (yet to be defined) performance gain, we'll have to (potentially significantly) compromise binary size and, potentially, some other performance characteristics
What is your use-case and why do you need this feature?
I need to serialize objects with many Doubles in them. The JDK's default Double serialization is slow, particularly on Android phones.
I can use custom serializers of course, but I would rather have a fast default implementation.
Describe the solution you'd like
Use Daniel Lemire's fast_float algorithm for parsing Double instead of the JDK's default. The speedup is considerable, almost 4x on Android for my quick checks.
The text was updated successfully, but these errors were encountered: