Re: [ptp-dev] ptp-dev Digest, Vol 68, Issue 4

[Dieter <dieter.krachtus@xxxxxxxxxxxxxx>]

> Actually, I think a combination of dependency extraction and compression would be worth trying.
>
> Greg

You may have missed my first post (pasted below). I already did
dependency extraction followed by compression in the first test. The 1
MB jar is reduced to 350 kb by compression. The jar does not only
contain .class files and is not very big to begin with, so the
compression factor is not very high.

I should also add that pack200+Gzip compression takes some time. For a
1 MB file this is quite ok but compressing a 30 MB file takes very
long which may make a antecedent dependency extraction a must.

Dieter


On Sat, Oct 30, 2010 at 7:33 AM, Dieter <dieter.krachtus@xxxxxxxxxxxxxx> wrote:
> I did some intiail tests to reduce the jproxy size:
>
> Original jar: 30 MB
> http://129.206.117.40:2222/test/test.jar
>
>
> Automated dependency analysis (only necessary .class file in jar): 1 MB
> http://129.206.117.40:2222/test/test-minimal.jar
>
> Dep. analysis + pack200 + Gzip: 350 KB
> http://129.206.117.40:2222/test/test-minimal.pack.gz
>
>
> Can somebody please test if test-minimal.jar is still functional and
> if not if it is due to missing .class or resource files.
>
> Cheers,
> Dieter