Usability Performance Discussion

Usability/Performance

This page will feature ideas for improvement regarding the introspection and change detection central to the extension functionality.

Related discussion: https://github.com/rev087/ng-inspector/issues/85

Performance Problem

This problem exists in both ng-inspector and Batarang.

ng-inspector

The main issue is that it adds too many watchers. It adds a single deep watch to every scope.

Batarang

The main issue is that it has to serialize big objects, creates large GC pauses.

Informative initial view

In ng-inspector, one thing users requested was that models were initially expanded. This made it easy to (at a quick glance) get a high-level view of the shape of the models on a scope.

However, this has a performance tradeoff. For Batarang, this means sending more info through different contexts. For ng-inspector, this means rendering more often.

Proposed solutions

Instrumentation should send over enough information to populate the screen immediately.