Community
Participate
Working Groups
This is likely even more far reaching than the UI, but I found it there. If you search for things in the p2 UI you will notice it's really slow. I spent some time on this today, and it turns out that the problem is in computing categories. When you search for things, all categories are expanded and this is the performance hit we are seeing. This is because the capability index is never used, and for each category we check each IU to see if it fits. It appears that the index is expecting us to look for 'provided capabilities' but instead we are checking to see if an IU 'satisfies' a requirement. Since this is not something the index knows about, it's not use. However, if we pull the query apart a bit and realize that it's actually just IRequirements[], we can actually make use of the index and this increases performance dramatically.
Created attachment 209163 [details] Patch v1 Here is a patch. I wonder if someone with more query experience can give this a look over?
*** Bug 263966 has been marked as a duplicate of this bug. ***
Released the attached patch.