|
Re: Materialize from ganymede update site downloads ever feature [message #380785 is a reply to message #380441] |
Mon, 03 November 2008 21:48 |
|
Hi Rich,
The pack200 is an compression algorithm specifically targeted against Java class files.
It's not related to digesting repository meta-data.
The really cool thing that indeed will give us a real boost is the new Equinox P2
technology and its meta-data repository. The work of P2'izing Buckminster imports etc. is
in progress but it's not finished yet.
Regards,
Thomas Hallgren
Rich Scott wrote:
> I am doing a materialize for several plugins using the eclipse.import
> reader with the uri set to the ganymede update site
> (http://download.eclipse.org/releases/ganymede). While the process is
> working it takes about 20 min. The console output shows that every
> feature listed in the site.xml is being downloaded. I am assuming that
> this is being done to look at the manifests.
>
> My understanding is that with Calisto, the concept of site optimization
> was introduced to remove the need for every feature to be downloaded.
> The Ganymede site appears to be optimized (<site pack200="true"> in
> site.xml). Does buckminster not use the optimized digest? Or is there
> something that I need to set in the mspec so that the optimizations are
> used?
>
> Any insights would be appreciated.
>
> Thanks
> Rich
>
|
|
|
|
Re: Materialize from ganymede update site downloads every feature [message #380793 is a reply to message #380791] |
Tue, 04 November 2008 12:11 |
|
Hi Rich,
As the page says. There are two parts.
1. Pack200
2. Site digesting.
Those two are not related. The Pack200 reduces the size of jar files significantly since
it performs optimizations based on internal knowledge of binary Java class files. The
digest could be helpful and give us a performance boost but I don't think its complete.
It's merely a concatenation of the feature.xml of the features listed in the site.xml. It
does not contain sub-features, nor does it contain the plug-in manifests. So it's a
tradeoff for us. Do we want to put more efforts into optimizing the old formant or do we
want to use the new P2 technology.
If you want to have a go at optimizing using the digest.zip and submit a patch, I'd be
happy to apply it.
Regards,
Thomas Hallgren
Rich Scott wrote:
> Thomas,
>
> Thanks for the update. I had gotten the impression from the wiki (
> http://wiki.eclipse.org/index.php/Update_Site_Optimization ) that
> pack200 was also used to create a single digest file that could be
> downloaded instead of the individual jars. The Ganymede Simultaneous
> Release site
> ( http://wiki.eclipse.org/index.php/Ganymede_Simultaneous_Rele ase ) also
> indicates that sites "should do site digesting". Which I misinterpreted
> to mean that the single digest could be downloaded instead of
> downloading all of the feature jars.
>
> It will be nice to get P2 incorporated into buckminster. I'm looking for
> to that change.
>
> Thanks
> Rich
>
>
> Thomas Hallgren wrote:
>
>> Hi Rich,
>> The pack200 is an compression algorithm specifically targeted against
>> Java
> class files.
>> It's not related to digesting repository meta-data.
>
>> The really cool thing that indeed will give us a real boost is the new
> Equinox P2
>> technology and its meta-data repository. The work of P2'izing Buckminster
> imports etc. is
>> in progress but it's not finished yet.
>
>> Regards,
>> Thomas Hallgren
>
>
>
|
|
|
|
Powered by
FUDForum. Page generated in 0.03012 seconds