RumbleDB/rumble

TODOs for JSON parsing

Opened this issue · 1 comments

  • Try out to introduce an internal JSON parsing API, and check for performance
  • Reuse JsonReader object across calls (requires carefully serializing/deserializing it so it works within each executor)
  • compare performance with gson as well as with previous jsoniter version

Reading the latest release docs, it seems you've switched to gson, so last point on your to-do list must be done - perhaps the others are as well?