mobject-json - cycle time

[FellowWithLaptop]

You could save a massive amount of cycle time if you don't recreate the json path with dynmaically created function blocks, but call the FindMember method directly while parsing the path.

[benhar-dev]

Good morning @FellowWithLaptop, ignoring the TryRead with string, then they are clocking in at around 7.5us - 8.5us (with all the string parsing + json lookup). Do you have an example of the code you you can share with me with the FindMember I can use to compare? I can run it through the RealTimeMonitor in the same way.

I'm also planning to add support for the other JsonPath syntax such as wild cards and queries which may result in returning multiple values such as array of values, so any recommendations would need to have this in mind for the future of the class.