realtimechris

4 ms·

1.
by realtimechris 2y ago
No, you only require division for digit-counts greater than or equal to 10: https://github.com/RealTimeChris/Jsonifier/blob/dev/Include/...
2.
by realtimechris 2y ago
So we can properly dispatch the correct length-based function with minimal branching to detect which length to serialize for: https://github.com/RealTimeChris/Jsonifier/blob/dev/Include/...
3.
Optimizing uint64_t Digit Counting: A Method that Beats Lemire's by up to 143%(github.com)
70 points by realtimechris 2y ago|29 comments
4.
by realtimechris 2y ago
*Optimizing uint64_t Digit Counting: A New Method that Beats Lemire's by Up to 27%* In the quest to improve the performance of my high-speed JSON library, JSONIFIER, I recently stumbled upon a breakthrough in optimizing the calculation
5.
by realtimechris 2y ago
It has reflection for the member names as well as compile-time hash maps for storing the locations to be parsed into/serialized from.
6.
Jsonifier, the Fastest and a New JSON Parsing/Serializing Library, in C++(github.com)
2 points by realtimechris 2y ago|3 comments
7.
by realtimechris 2y ago
Here is a json parser/serializer that I've been working on for about a year or so now. There is benchmarks available at https://github.com/RealTimeChris/Json-Performance comparing it to the other 2 most perfo
8.
by realtimechris 3y ago
As you can see - the parser/serializer I've developed uses the minimal possible memory allocations. Nice parser though.
9.
Jsonifier, The Fastest and A New JSON Parsing/Serializing Library, in C++(github.com)
2 points by realtimechris 3y ago|5 comments
10.
by realtimechris 3y ago
Hey everyone - so I've taken simdjson's algorithm and improved upon it by resaturating the CPU registers with data instead of only operating on 64-bytes worth of string data at a time, as well as incorporated some compile-time has