[CT-3336] [Test Performance] Optimize the set_up_plugin_manager() function #9029
Labels
performance
tech_debt
Behind-the-scenes changes, with little direct impact on end-user functionality
Short description
Profiling shows that the set_up_plugin_manager() function takes up 30% of the runtime on the main thread during integration testing. The hot path is set_up_plugin_manager() -> from_modules() -> iter_modules(). By caching the results we need after the first time iter_modules() is called, nearly all this time can be won back.
Acceptance criteria
Impact to Other Teams
None. They may enjoy the speedier tests, though.
Will backports be required?
No.
The text was updated successfully, but these errors were encountered: