Community
Participate
Working Groups
Let's say you have the following setup: Server A: - Contains site.xml which points to all features, plugins, and archive data on Server B. Server B: - Contains the features, plugins, and archive data files. Eclipse Workbench Software Update Perspective: - Has a discovery URL that show up under the Sites to Visit folder. - This discovery URL points to the site.xml on Server A. The problem here is that it takes a lengthy amount of time after clicking on the discovery URL to connect to Server A/B and read the site.xml. Maybe 5 minutes or more. After the 5 minutes, you'll be able to see the categories on the site. If you click on the category you'll be forced to wait another 5 mins to see the list of features for that category show up. Clicking on the feature will start the download. The downloads appear to not suffer any lag and happen immediately. Why are the sites so slow to load? Can this be improved/enhanced so the user does not have to wait?
Action Taken: can you provide a feature with the discovery sites to test ? Action Plan: investigate as part of M4 peformance
Another thought (forgot to add this in the original description): As an alternative (if the speed cannot be improved), could a progress bar or status window appear in some form where the user can get visual feedback?
It seems most of the time (20 seconds out of 30) is spent opening the connection to download JAR file to retrieve the label of the feature. *** This bug has been marked as a duplicate of 26943 ***
