
Signature
martin@ | Martin Gregorie
gregorie. | Essex, UK
org |
pon, 17 kwi 2006 o 13:49 GMT, Martin Gregorie napisał(a):
> JAR files will reduce i/o overheads (only one file to open, less to read
> if compressed).
but even loading not compressed jar makes overheads, because loader must
interpret jar(zip) file, but that overheads are so small, so it can be omitted
Pozdrawiam
Brzezi

Signature
[ E-mail: brzezi@enter.net.pl ][ GEEK CODE [Version: 3.12]: GCM dpu s+:- ]
[ Ekg: #3781111 ][ a--- C+++ UL++ P+ L+++ E--- W+++ N+++ ]
[ LinuxUser: #249916 ][ o-- K- w--- O-- M- V- PS PE Y PGP--- t+ ]
[ 5- X++ R* tv+ b- DI- D+ G+ e- h! r y-- ]
Martin Gregorie - 17 Apr 2006 18:47 GMT
> pon, 17 kwi 2006 o 13:49 GMT, Martin Gregorie napisał(a):
>
[quoted text clipped - 3 lines]
> but even loading not compressed jar makes overheads, because loader must
> interpret jar(zip) file, but that overheads are so small, so it can be omitted
Depends on your hardware and software. Both must be considered:
- If your CPU is fast but you're using an OS with slow i/o
(e.g. Windows 9x) the JAR file most likely be faster.
- If your CPU is slow (<300 MHz) but your OS has fast, multi-threaded
i/o (e.g Linux) the chances are that using a JAR file is slower.
- If you're reading the classes over a comms line then the JAR file
will almost always be faster.

Signature
martin@ | Martin Gregorie
gregorie. | Essex, UK
org |