0

I am running some computationally expensive jobs, and would like to run them in the fastest way possible. I have three options:

  1. ssh from workstation A in network A (Ubuntu) into workstations B, C, D etc in network B (Centos) to run the jobs
  2. physically walk to workstation B in network B and ssh into workstations C, D etc to run the jobs
  3. physically walk to each workstation to run the jobs

Would they all run at the same speed? If not, which would be the fastest, and why?

Christian Seitz
  • 138
  • 5
  • 1
    In all three options the performance of the workstations should be the same. One thing to note is, if you use ssh and you put a high load on the workstation, your session could be slow. – Rattlehead Jan 16 '20 at 08:00
  • 1
    There would be a difference if you have to transfer large amounts of data and the network is slow, in which case a USB disk and a pair of sneakers could have a lot more bandwidth. – xenoid Jan 16 '20 at 12:25
  • *"I am running some computationally expensive jobs"* -- You probably mean computationally *intensive*. – sawdust Jan 16 '20 at 21:05

1 Answers1

2

I recommend using version 1., but with a twist: Use a session managemnet tool like screen, tmux and friends.

This solves two problems:

  • If the console output from a job is faster than your network speed, the job will indeed slow down (rather not likely in a LAN, but may easily be over the internet). By detaching from your screen session this problem goes away.
  • If you drop your SSH connection (e.g. by fat-fingering), the remote job will catch a SIGHUP and will end. If you use screen, it will keep running and you can later reattach.
Eugen Rieck
  • 19,950
  • 5
  • 51
  • 46