John Rice wrote:
Shawn Walker wrote:
jmr wrote:
Padraig - as this is post 2009.06, I'd like us to review all the Tab
panels and decide what they should look like. As we are introducing a
Tree View to get around l10n layout issues, I think we could use the
installed icon in the Dependencies tab if we also change it to use
the Tree View. We should review all this with Jenya.
Whatever we do its good to know the performance is not an issue here
for fetch and display this info.
There should no longer be a performance issue in calling api_o.info()
to obtain package information. In fact, if done properly, there
should no longer be a need for the GUI to cache this information as
manifest accesses are very cheap now.
So Shawn is it now very cheap for me to access manifest data such as
description of packages that are not installed on the system, but in the
repository? If this is the case then great, I would be delighted to
remove the cache, if not then we still have a problem.
Once the system has cached the manifest, it should be.
However, I would note that you will get better performance if you call
api.info() with a list of *all* the packages you want information for
instead of one at a time. You'll also want to call it with a
frozenset() for info_needed that only specifies the information you want.
There's also an opportunity for a slight optimisation in info such that
if you specify local=False, and the client already has a manifest, it
doesn't need to check_cert_validity().
There are three key changes I'd like to see in the GUI post 2009.06:
* Elimination of cache
* Change to --not-- load information of all packages in memory
Same issue as above, how do you propose that we get information on
packages that are in the repo but not installed on the system in a
timely manner?
See above. However, what I was talking about here is the GUI's current
behaviour of loading all descriptions for all packages into memory on
startup (albeit using threading). It should really only have the
information about packages that are currently visible to the user.
Cheers,
--
Shawn Walker
_______________________________________________
pkg-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
