The impact of encryption very much depends on the instruction set of your CPU 
(Intel AES-NI) and whether your library
will use those. If you have a recent enough CPU you won't see much difference 
between normal SSH and HPN-SSH…



Am 02.06.2015 um 20:10 schrieb John Lockman:
> This is a bit off topic for the slurm-dev group, but using HPN-SSH will 
> likely speed up your data movement:
> http://www.psc.edu/index.php/hpn-ssh
> 
> Turn off encryption, use less CPU, go faster :)
> 
> On Tue, Jun 2, 2015 at 12:07 PM, Jared David Baker <[email protected] 
> <mailto:[email protected]>> wrote:
> 
>     Bipin,____
> 
>     __ __
> 
>     Perhaps I’m missing something, but I don’t necessarily see why you’d 
> really need Slurm for this task. Seems like a
>     fairly straight forward backup task. Are you trying to limit the amount 
> of networking being used or something
>     similar?____
> 
>     __ __
> 
>     -Jared____
> 
>     __ __
> 
>     *From:*Bipin Shetty [mailto:[email protected] 
> <mailto:[email protected]>]
>     *Sent:* Tuesday, June 02, 2015 10:15 AM
>     *To:* slurm-dev
>     *Subject:* [slurm-dev] Request information for our current tasks - Need 
> inputs - IMPORTANT
>     *Importance:* High____
> 
>     __ __
> 
>     Hi Slurm Team,____
> 
>     __ __
> 
>     As part of our research for workload management we found SLURM to be a 
> very effective solution. I would like to
>     understand more about this solution if it really fits into our scheme of 
> things and would like to take it forward
>     with your valuable suggestions.____
> 
>     __ __
> 
>     Following is our scenario we have today:____
> 
>     __ __
> 
>     __1.       __We pull approx 3 TB of data every day from our production 
> linux servers to a backup linux machine which
>     takes almost 2-3 hours everyday.____
> 
>     __2.       __Currently we are using simple Unix scripts to pull the data 
> from the production servers to the backup
>     linux machine. We have the script pulling data from all servers using SCP 
> protocol.____
> 
>     __3.       __Post that we perform operations on the pulled data and then 
> spilt that into multiple chunks and delete
>     the original 3 TB data.____
> 
>     __4.       __This whole process eats up our network big time due to the 
> heavy workload involved.____
> 
>     __ __
> 
>     Need your inputs or help to let me know if Slurm would be  the right 
> solution for us to take this forward. Also, do
>     let me know if you need any additional inputs from me. ____
> 
>     __ __
> 
>     We are running against time to get a solution implemented in production. 
> Would be great if you can respond at the
>     earliest with your suggestions.____
> 
>     __ __
> 
>     Appreciate your time. Have a wonderful day ahead!!. ____
> 
>     __ __
> 
>     Warm Regards____
> 
>     *BIPIN____*
> 
>     —    ____
> 
>     *Sapient**Nitro*____
> 
>     *mobile  *5712512175 <tel:5712512175>*____*
> 
>     __ __
> 
>     The information transmitted is intended only for the person or entity to 
> which it is addressed and may contain
>     confidential and/or privileged material. Any review, retransmission, 
> dissemination or other use of, or taking of any
>     action in reliance upon, this information by persons or entities other 
> than the intended recipient is prohibited. If
>     you received this in error, please contact the sender and delete the 
> material from any computer.____
> 
>     __ __
> 
> 
> 
> 
> -- 
> John Lockman III
> CTO / HPC Software Specialist
> [email protected] <mailto:[email protected]> - 512.903.0951
> 
> 

Reply via email to