Community
Participate
Working Groups
If a user clicks on each of the tabs it seems like the content is not cached. For performance reason the client should cache the content of the tabs.
A bug was causing screenshot images to be reloaded every time solutions were retrieved from the marketplace. A caching strategy has been implemented that reduces the need for queries to the marketplace REST service.
Created attachment 167072 [details] mylyn/context/zip
Marketplace still seems to be fetching the list each time you swap back and forth between tabs. In order for this to be scalable with the number of connections we need for the main queries, featured, popular, recent to be cached for at least the duration of the MPC's lifetime.
(In reply to comment #3) > Marketplace still seems to be fetching the list each time you swap back and > forth between tabs. MPC caches server responses for the lifetime of the MPC dialog. As soon as you close/reopen the dialog all previously cached results are discarded. A maximum of 30 requests are cached: when this number is exceeded the least recently used request is removed from the cache. MPC also performs other kinds of requests: * retrieving images (screenshots, icons) * check for updates * verify availability (site verifier) The site verifier is run by p2 and hits the respective update sites of nodes that have ius specified. The results of check for updates are cached on a per-node basis for the lifetime of the dialog. Images are cached also. As far as I know the only component here that is not using caching is the p2 site verifier. In my testing here it all seems to be working for me. Do you have a specific set of steps to reproduce?
Fixed, please reopen if you continue to see problems with version 1.0.0.v20100520-0117 or later.