Community
Participate
Working Groups
Loading the profile preference node is currently loading the full-blown IProfile object from the profile registry. This is expensive and unnecessary.
Created attachment 132135 [details] Profiler output
I'm glad you brought this up, because in bug 222498 comment 4, we determinded that we have to load those preferences in bundle startup code, which means the expensive profile code is being run in startup. :-(
Yes, this is why I noticed it. I was profiling the automated "UI startup" performance test from the latest nightly build and noticed a big hit here.
Fixed in HEAD. This required adding a new method IProfileRegistry.contains to check for existence of a profile on disk without actually loading it.