| Sanne Grinovero This, and especially JSON streaming, is definitely 6.x material. There is a number of design facts that, right now, require random access to the JSON structures. Careful if choosing something else than GSON though: we're using some features of GSON (like TypeAdapters) which may not be present in performance-focused libraries. On the other hand, I think one improvement we could roll quite easily is avoid JSON parsing altogether in some cases. For instance, right now when we create a document and receive a HTTP status 200 response, we parse the response, but we don't do anything about it. We probably could avoid this parsing. Not sure the performance impact would be high though, since we try to bulk such requests, and when receiving a bulk response we definitely need to parse the response.
I'll create a ticket to investigate that:
 HSEARCH-2819 Open |
