3 ms·
> If you roll your own, it'll be about 10x less efficient than something done properly using SIMD instructions. Is this really an issue when loading a field fr
by secondcoming 6y ago
> If you roll your own, it'll be about 10x less efficient than something done properly using SIMD instructions.
Is this really an issue when loading a field from a config file? If it was something happening 1m times per second then maybe I could see your point.
- jiggawatts 6y agoJSON is now at the point where yes, it does makes sense to optimise it with AVX2 instructions. https://github.com/simdjson/simdjson https://github.com/simdjson/simdjson
- curryst 6y agoJSON is in a slightly different area since it's commonly used as a serialization format for RPC/REST so it's in a hot path. Optimizations there make a lot of sense; optimizations on reading your configuration file are almost certainly premature optimizations. The fact that your config will load some tiny amount faster with those optimizations is a side effect of the hot path optimizations, not a requirement for config formats.