[kepler-dev] [Bug 1836] - search performance problems/bugs

bugzilla-daemon@ecoinformatics.org bugzilla-daemon at ecoinformatics.org
Thu Dec 16 07:50:44 PST 2004


------- Additional Comments From rods at ku.edu  2004-12-16 07:50 -------
One of the reasons DiGIR is slow is because we ALWAYS hit all 10 or providers
and have to wait for all the resultsets to come back before it can return any

This "should" be improved once we have metadata in the regisrty and enable the
users to be more selective about where they want to search.

If they don't want to be selective and want to get all the data from everywhere
then it will take a while. This has partically to do with setting the user's
expectations about the task they are performing. We know what it is doing behind
the scenes so we have a different set of expectations.

They have no idea the amount of data that is being searched and how it is
collected and combined and returned.

More information about the Kepler-dev mailing list