Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
QuerySelectorAll - performance
See original GitHub issueI try to profile my app because i facing issue with performance (main reason why i recently switch from HAP). And i notice NodeList.get_Length() in QuerySelectorAll is take lot of time (almost 10%). Of course it depend on how much elements is in collection).
I want to try rewrite it with my custom QuerySelectorAll but i end with too many class is need to rewrite. Maybe you can try just save elements.Length to local variable it should get some percent of performance in this highly used function.
Testing with last stable version 0.9.9 but from first look at dev branch i think it is same in 0.1.0. VS 2017 - release mode of course
Issue Analytics
- State:
- Created 6 years ago
- Comments:6 (4 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Great, thanks!
Ok here is the gist.
https://gist.github.com/jirisykora83/d1316a636d5f6c154872cc746c7654a1