Performance: Alternative strategies for tracked properties

[joeljeske]

I have a complex application with many (1000+) active queries, and have noticed that a decent amount of time is spent in QueryObserver.trackResult. I notice that the mechanism used to trap property get's is using Object.defineProperty. I was contemplating alternative mechanisms for tracking property calls, and ran a performance analysis on them here: jsbenchmark .

We may be able to dramatically improve the performance of this part of the code using either a static class with getters defined, or perhaps a JS Proxy to trap get calls.

Has this be considered before?

[joeljeske]

FYI, I create PR to reflect the Proxy idea, which is a most similar to today's state.
#8092