Property Tree Performance
Jump to navigation
Jump to search
| This article is a stub. You can help the wiki by expanding it. |
Background
getNode("foo") and getChild("bar") consumes CPU while setFloatValue() seems to be quick.[1]
Property name lookups are slow, there are some tricks to optimise that we could do, especially using a global hot cache. This would also allow an easy way to fix problem cases, by taking the hottest entries and fixing their call sites to cache the node. The first thing, however, is extending the existing unit test to do some basic benchmarking of reads & writes, and name lookups. And then the same but in the presence of narrow and broad listeners. [2]
References
References
|