Change order of reps to speedup getRep
Categories
(DevTools :: Object Inspector, task, P3)
Tracking
(Not tracked)
People
(Reporter: nchevobbe, Assigned: nchevobbe)
References
Details
(Whiteboard: dt-console-perf-2022)
Attachments
(1 file)
getRep goes through a list of components (devtools/client/shared/components/reps/reps/rep.js#45-81 and check for each one if their supportObjects function returns true for a given grip.
The order in which reps are iterated is not optimal, and we could probably re-order them so we check the components that are most likely to be used first (String, Number, Grip, …)
| Assignee | ||
Comment 1•3 years ago
|
||
This patch makes it so we iterate over the components that are most likely to
be used first (string, number, objects, …)
Comment 2•3 years ago
|
||
There's a r+ patch which didn't land and no activity in this bug for 2 weeks.
:nchevobbe, could you have a look please?
If you still have some work to do, you can add an action "Plan Changes" in Phabricator.
For more information, please visit auto_nag documentation.
Comment 3•3 years ago
|
||
Nicolas, can we land the patch? Or are there any blockers?
| Assignee | ||
Comment 4•3 years ago
|
||
I had to fix a few test failures, and I wanted to wait on my work to automatically generate stubs before landing it. This will also conflict with Bug 1759135, which I'd rather land first
Updated•3 months ago
|
Description
•