Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
[ptp-dev] java proxy dependencies

On Tue, Nov 2, 2010 at 5:59 PM,  <ptp-dev-request@xxxxxxxxxxx> wrote:
> Send ptp-dev mailing list submissions to
>        ptp-dev@xxxxxxxxxxx
>
> To subscribe or unsubscribe via the World Wide Web, visit
>        https://dev.eclipse.org/mailman/listinfo/ptp-dev
> or, via email, send a message with subject or body 'help' to
>        ptp-dev-request@xxxxxxxxxxx
>
> You can reach the person managing the list at
>        ptp-dev-owner@xxxxxxxxxxx
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of ptp-dev digest..."
>
>
> Today's Topics:
>
>   1. Re: ptp-dev Digest, Vol 68, Issue 4 (Dieter)
>   2. Re: ptp-dev Digest, Vol 68, Issue 4 (Greg Watson)
>   3. Re: PTP 4.0.4 build available (Jay Alameda)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Tue, 2 Nov 2010 17:26:03 +0100
> From: Dieter <dieter.krachtus@xxxxxxxxxxxxxx>
> To: ptp-dev@xxxxxxxxxxx
> Subject: Re: [ptp-dev] ptp-dev Digest, Vol 68, Issue 4
> Message-ID:
>        <AANLkTi=F4tczFnHe3O5k14Gd_oG5NjJAowTsy--Ni_0J@xxxxxxxxxxxxxx>
> Content-Type: text/plain; charset=ISO-8859-1
>
>> 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
>
>
> ------------------------------
>
> Message: 2
> Date: Tue, 2 Nov 2010 12:40:12 -0400
> From: Greg Watson <g.watson@xxxxxxxxxxxx>
> To: Parallel Tools Platform general developers <ptp-dev@xxxxxxxxxxx>
> Subject: Re: [ptp-dev] ptp-dev Digest, Vol 68, Issue 4
> Message-ID: <6EF7D652-E0FE-447F-9DF4-F47B58492187@xxxxxxxxxxxx>
> Content-Type: text/plain; charset=us-ascii
>
> So for the actual pbs server jar, do you know how long it will take and what the resulting file size will be?
>
> Thanks,
> Greg

I think this jar is a realistic example of a pbs server jar 'polluted'
with unecessary files since it was created using the Eclipse export
mechanism that includes all dependend projects:
http://129.206.117.40:2222/test/test.jar, size: 30 MB

Extracting this jar takes a very long time. My performance tests do
not include extracting the jar but I assume that the content of that
jar is already available in a single folder.
I don't know enough about the build process used at the moment but I
guess all the files, including those for the pbs server are available
at some point in a single folder? Is this the case?

Starting with a folder containing all files: .class, images, .dll,
.properties, etc.

Results:
Dependency analysis ~1 sec.
Creating a jar ~3 sec. (size: 1 MB)
Compressing this jar (pack200+Gzip) ~1 sec. (size ~350 kb)

The pbs server should therefore be below 500 kb.

Cheers,
Dieter


Back to the top