Re: [cross-project-issues-dev] Its not too late to condition your jars f

[David M Williams <david_williams@xxxxxxxxxx>]

For what is worth ... to follow the
"download" statistics with "installed" statistics,

I just installed "everything"
(Callisto RC4, starting with Platform Binary runtime) on my windows system,

and looks like we are currently at 598
plugins installed .... can't someone come up with two more? :) 
Which is roughly 187 MBytes .. 198MBytes
"on disk" size (NTFS) with 
exactly 500 of the plugins being the
"jarred up" variety, and ~only~ ? 98 plugins still in folders.

David M Williams/Raleigh/IBM@IBMUS
Sent by: cross-project-issues-dev-bounces@xxxxxxxxxxx

06/07/2006 12:07 AM

Please respond to
Cross project issues <cross-project-issues-dev@xxxxxxxxxxx>

To	Cross project issues <cross-project-issues-dev@xxxxxxxxxxx>
cc
Subject	[cross-project-issues-dev] Its not too late to condition your jars        for pack200!

Well, that is, if you can fix your build scripts, but hope everyone 
has been looking into it and ... everyone's about done 
with the other hard stuff, right? :) 

I've computed some numbers and the savings is pretty sizable, 30% currently,
and 
this could be expected to go up to 60% savings if everyone packed (conditioned)
their 
update site jars. I've put some of these numbers in "info" bug
145685, and 
pasted the text below. Feel free to comment there (or here) or add your
own numbers! 

If it helps anyone transition, I've put part of our WTP build script right
in 
our wiki, at 

http://wiki.eclipse.org/index.php/Callisto_Build_and_Update_Tips_and_Tricks

that documents how we do it in WTP. It may not apply directly, depending
on 
how you do your builds, but I've broken it up into 6 "utility steps",
and even 
annotated the ant script! -- I'm sure you'll enjoy reading it, even if
you don't 
implement it :) [And, thanks go to Andrew, Richard, Sonia, Kim and Naci
for doing 
all the hard stuff and setting good examples ... I just pulled things into
one spot and wrote the comments :) ] 

So, be sure to ask if you run into trouble packing up stuff ... I'm sure
there's 
readers of this list that would be very happy to help. 


= = = = = 
https://bugs.eclipse.org/bugs/show_bug.cgi?id=145685
= = = = = 

This is an "info" bugzilla only, to document the size of Callisto
(as of RC4)
and the effects of using Pack200. I will attach an excel spreadsheet that
contains the "raw data" that lead to this summary, in case anyone
else want to
play with them, or do a more detailed analysis. 

There are 645 jars "available" for download (some are platform
specific, so no
one would ever download them all -- though I'll act like they would for
some of
the following summaries). 

The total size of all those 645 jars is 194 MBytes. (So, imagine, that's
what
would be downloaded if pack200 not available, and someone needed them all).

I think only the Eclipse Project and the WTP project have conditioned their
jars (as of RC4) which leads to about half of those jars having packed
(.gz) 
versions available. 

The total size of all the packed (.gz) files is 47 MBytes. 
The total size of the jars that correspond to these gz files is 107 MBytes.

This means that "packing" in general, on average, produces .gz
files that are
44% the size of their corresponding jars. 

If instead you take as the-total-to-include all the files that would need
to be
downloaded, the packed version is 70% of that total (so, if most users
have
'unpack' available, and if most users used update manager, you can thank
the
WTP and Eclipse Projects for saving 30% bandwidth in the upcoming release
:)
But if everyone did it, the saving would be about double that! Hmmm, what's
that translate into rented bandwidth costs? :) 

It is very interesting that on a jar by jar basis, the reduced size varied
everywhere from 20% to 90% of the original jar (with the 44% being a
real-life-in-practice average). As would be expected, "doc" plugins
did not
compress well, and very small code plugins did not compress well. 

Hope everyone finds these interesting as I do! 

_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev