Menu

#2 JADE client receive operation is taking 28 times more than normal SCP operation for 1 GB file transfer

None
closed
nobody
None
1
2015-02-13
2014-03-27
No

We are using JADE version 1.5.4014 in our test setup.

Trying to send get one 1 GB file from one server node (Linux) to anothe server node (Linux)
under the same network using SFTP Receive operation.

It took 28 mins.

Where as when we tried the same with the SCP command from OS command prmopt (without using JADE) and perform get operation , it took less than 1 min(around 44 secs). That indicates infrastrucutre is not adding the delays.

JADE Log indicates there is an MD5 hashing operation performed and most likely it is responsible for the adding that addtional delay. Attached is the log.

we tried to disable couple of params in JADE INI file
1) CreateSecurityHashFile=false
2) CheckSecurityHash=false

But it did not work.

Can you please suggest a solution/work around for that?

thanks,
RP

Discussion

  • Rahul Purkayastha

    Attached is the JADE log

     
  • SOSMP

    SOSMP - 2014-03-27

    JADE is by default using an old SSH implementation which could be the reason for the slow performance. ( Next JADE release will use improved SSH implementation)

    add following parameter in your profile depending upon your configuration

    loadClassName=com.sos.VirtualFileSystem.SFTP.SOSVfsSFtpJCraft
    or
    sourcd_loadClassName=com.sos.VirtualFileSystem.SFTP.SOSVfsSFtpJCraft

     
  • SOSMP

    SOSMP - 2014-03-28

    correction : wrong spelling of source :(

    loadClassName=com.sos.VirtualFileSystem.SFTP.SOSVfsSFtpJCraft
    or
    source_loadClassName=com.sos.VirtualFileSystem.SFTP.SOSVfsSFtpJCraft

     
  • SOSMP

    SOSMP - 2014-03-28

    here I am again ..
    If you are using host/local_dir type profile ,
    use
    target_loadClassName=com.sos.VirtualFileSystem.SFTP.SOSVfsSFtpJCraft

    It will be interesting to see if you can post back , if it work for you.

     
  • Uwe Risse

    Uwe Risse - 2015-02-13
    • status: open --> closed
    • Group: -->
     

Log in to post a comment.

MongoDB Logo MongoDB