Actions
Bug #5229
closedPoor component search performance
Start date:
10/28/2010
Due date:
% Done:
0%
Estimated time:
Bugzilla-Id:
5229
Description
Here is email from Matt:
Hi Jing,
Another thing about Kepler -- I noticed that that the search for remote components is 1) painfully slow, 2) has not search status indicator, and 3) seems to freeze up the app while it is searching. These things combined make for a painful user experience.
Matt also mentioned we should double check if every search is doing a Metacat read on every matching kars. If it does, we may change this to a single hit on metacat.
Related issues
Actions