in reply to Re: Net::SSH::Perl and fork hangs
in thread Net::SSH::Perl and fork hangs

If I don't share the handle, I will have to initiate a new Net::SSH::Perl connection in child process and that will slow down the execution of my test case. I have a requirement to execute the same cmd on n number of hosts. I do have a workaround of using system(), instead of Net::SSH::perl. But using system() is slow. Thanks for your suggestion.

Replies are listed 'Best First'.
Re^3: Net::SSH::Perl and fork hangs
by Old_Gray_Bear (Bishop) on Jun 02, 2014 at 19:11 UTC
    Which runs slower? a) A new connection + system() or b) A Code that hangs and never completes?

    And, since this is a 'test'case', why is there an artificial constraint on the amount of time it takes? Tests typically need run to completion, how ever long that is. There are better things to focus your optimization efforts upon.

    Update: Looking through the old diaries I found the test logs from a gig I had at a bank in 1995. We were happy when the one test that exercised all of the databases, some 20+ Oracle DBs, completed in under 17 hours. Now we only ran it once a month as part of the regression testing, but....

    ----
    I Go Back to Sleep, Now.

    OGB

[reply]
[d/l]

      The focus is on test execution time also. There will be 100's of test cases and each test case will have several cmds to be executed over n number of nodes. Currently using Net::SSH::Perl, my test case takes 6 secs to run on 3 different hosts involving a total of 70 system cmds. I am very happy with Net::SSH::Perl module. But multithreading with Net::SSH::Perl gives segv when I try to join the thread. That's why I was experimenting with fork and exec. Multithreading with Net::OpenSSH works fine. And so also fork and exec. Perhaps will have to switch to Net::OpenSSH instead of Net::SSH::Perl

[reply]
Re^3: Net::SSH::Perl and fork hangs
by salva (Canon) on Jun 02, 2014 at 19:10 UTC
[reply]

In Section Seekers of Perl Wisdom