JSAGA

Hi Lionel!

Last year we wrote some articles about Data Avenue we implemented that relies on jsaga, and had to do some
performance tests. To summarize the results, jsaga performs well compared to "dedicated tools" (sftp, globus-url-copy) -
we measured tansfer rates at reading/writing from/to streams through jsaga (FileFactory.createFileInputStream(session, url)).
The results below are not precise enough, as it (100MB/total transfer time) contains connection establishment time as well (not just data transfer time):

Download and upload times of a file of size 100MB using proprietary tools (sftp, globus-url-copy)
SFTP 12.6 s (7.94 MB/s) 6.5 s (15.4 MB/s)
GSIFTP 0.535 s (187 MB/s) 1.613 s (62 MB/s)

Input/output stream reading/writing speeds using the JSAGA APIs
Read Write
SFTP 13.91 s (7.19 MB/s) 6.27 s (15.94 MB/s)
GSIFTP 0.66 s (151 MB/s) 2.72 s (36.82 MB/s)

Actually, I think jsaga could perform much better in the case of GridFTP if it could connect to
gridftp server faster. I experienced that it may take 2-3 seconds for jsaga before any operation (list, read stream) is done.
globus-url-copy does connection in less than 0.1 sec, also, CERN's WebFTS connects to gridftp server very fast.

It is not critical and urgent, but can you please check why it is so time consuming for jsaga to connect to a gridftp server?

Best regards,
Akos Hajnal