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
Working on application that allow the user to extract selective data from the result objects from JSON document using (list of) json path. We are using Jackson Tree model (JSonNode) to represent the data.
I've compared performance of json path on simple expression (e.g., a.b.c, or a[2].c, - no expressions, no filtering) vs Jackson jsonNode.at(...) - using JsonPointer. Notice JsonPointer to ourperform jsonpath for those cases by a ratio of 4X. To address the problem, we added conditional logic that check if the jsonpath is "simple", and convert it to jsonpointer lookup.
I suspect jsonPath engine does not have "fast" path to evaluate those queries. I wonder if will be possible to check if a given jsonPath is "simple", and in this case, use a faster implementation that will provide faster response time for those queries.
The text was updated successfully, but these errors were encountered:
Working on application that allow the user to extract selective data from the result objects from JSON document using (list of) json path. We are using Jackson Tree model (JSonNode) to represent the data.
I've compared performance of json path on simple expression (e.g., a.b.c, or a[2].c, - no expressions, no filtering) vs Jackson jsonNode.at(...) - using JsonPointer. Notice JsonPointer to ourperform jsonpath for those cases by a ratio of 4X. To address the problem, we added conditional logic that check if the jsonpath is "simple", and convert it to jsonpointer lookup.
I suspect jsonPath engine does not have "fast" path to evaluate those queries. I wonder if will be possible to check if a given jsonPath is "simple", and in this case, use a faster implementation that will provide faster response time for those queries.
The text was updated successfully, but these errors were encountered: