←back to thread

People still use our old-fashioned Unix login servers

(utcc.utoronto.ca)
90 points sugarpimpdorsey | 4 comments | 30 Jul 25 23:10 UTC | HN request time: 0.22s | source
Show context
teekert ◴[03 Aug 25 09:48 UTC] No.44775397[source]▶
Perhaps it is worth noting that all super computers I know (like the Dutch Snellius and the Finnish Lumi) are Slurm clusters with login nodes.

Bioinformaticians (among others) in (for example) University Medical Centers won’t get much more bang for the buck than on a well managed Slurm cluster (ie with GPU and Fat nodes etc to distinguish between compute loads). You buy the machines, they are utilized close to 100% over their life time.

replies(4): >>44775708 #>>44775996 #>>44777261 #>>44784010 #
janeway ◴[03 Aug 25 12:09 UTC] No.44775996[source]▶
Yes, I spend a majority of my professional life on similar systems writing code in vim and running massive jobs via slurm. Required for processing TBs of data on secured environments with seamless command line access. I hate web-based connections or vscode type system. Although open to any improvements, this works best to me. It’s like a world inside one’s head with a text-based interface.

Graphical data exploration and stats with R, python, etc is a beautiful challenge at that scale.

replies(2): >>44779805 #>>44799879 #
1. sevensor ◴[03 Aug 25 21:04 UTC] No.44779805[source]▶
Aside from how slow and user hostile it is compared to a text editor, my biggest complaint about vs code is the load it puts on the login node. You get 40 people each running multiple vs code servers and it brings the poor computer to its knees.
replies(2): >>44784127 #>>44799845 #
2. teekert ◴[04 Aug 25 10:52 UTC] No.44784127[source]▶
I know indeed that our sys-admins also don't like it.
3. mattpallissard ◴[05 Aug 25 16:06 UTC] No.44799845[source]▶
Every job on an HPC cluster should have a memory and CPU limit. Nearly every job should have a time limit as well. I/O throttling is a much trickier problem.

I wound up having a script for users on a jump host that would submit an sbatch job that ran sshd as the user on a random high level port and stored the port in the output. The output was available over NFS so the script parsed the port number and displayed the connection info to the user.

The user could then run a vscode server over ssh within the bounds of CPU/memory/time limits.

replies(1): >>44806988 #
4. sevensor ◴[06 Aug 25 02:32 UTC] No.44806988[source]▶
That’s a really cool idea!