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
When we are getting field decoders during entity reading, there is a field path being searched each time.
Since this happens dozens of times per entity the processing needed to search through the tree is sub optimal and consuming a lot of cycles.
A better solution would be using some flat dictionary with a hash of the field path that is very fast to compute to look them up.
Not sure entirely how this would look as I played around with somethings, but it should have a sort of flow of taking the field path, hashing it and seeing if it exists in a dictionary for the entity already and returning it right away if it does, otherwise get a serializer for the class and then resolve the decoder by path.
Can't really put more details about this as I am not sure what the end outcome will be, as this is not the only solution, but the goal is to expedite the process of resolving the field decoder based on the field path we are looking for.
Other solutions gladly welcome
The text was updated successfully, but these errors were encountered:
When we are getting field decoders during entity reading, there is a field path being searched each time.
Since this happens dozens of times per entity the processing needed to search through the tree is sub optimal and consuming a lot of cycles.
A better solution would be using some flat dictionary with a hash of the field path that is very fast to compute to look them up.
Not sure entirely how this would look as I played around with somethings, but it should have a sort of flow of taking the field path, hashing it and seeing if it exists in a dictionary for the entity already and returning it right away if it does, otherwise get a serializer for the class and then resolve the decoder by path.
Can't really put more details about this as I am not sure what the end outcome will be, as this is not the only solution, but the goal is to expedite the process of resolving the field decoder based on the field path we are looking for.
Other solutions gladly welcome
The text was updated successfully, but these errors were encountered: