28
edits
Changes
Jump to navigation
Jump to search
Line 1:
Line 1: − + Line 6:
Line 6: − ```+ − + − + − + − + − ``` + + + + + + + + + + + + + + + + + + + + + +
Info about the #windows Slack channel
The Sasha compute cluster contains contains several Windows VMs, which SSI members can use to run resource-intensive software, without relying on their personal computers. This also allows members with Apple computers to run Windows software without having to Dual-Boot. This approach also enables computationally intense jobs to be run for extended periods, as the cluster maintains nearly 100% uptime.
The sasha.stanford.edu compute cluster contains contains several Windows VMs, which SSI members can use to run resource-intensive software, without relying on their personal computers. This also allows members with Apple computers to run Windows software without having to Dual-Boot. This approach also enables computationally intense jobs to be run for extended periods, as the cluster maintains nearly 100% uptime.
==Performance==
==Performance==
For interactive workloads (CAD, Altium, etc.) the limiting factor for usability will be the users network connection to the cluster. Ever keyboard/mouse/screen interaction experience the latency added by your internet connection and Stanford's internet connection. For users on campus, this effect will likely be hard to notice, but for users around the world, there may be significant lag. You can test this latency by running the following command:
For interactive workloads (CAD, Altium, etc.) the limiting factor for usability will be the users network connection to the cluster. Ever keyboard/mouse/screen interaction experience the latency added by your internet connection and Stanford's internet connection. For users on campus, this effect will likely be hard to notice, but for users around the world, there may be significant lag. You can test this latency by running the following command:
timv@timv-5510:~$ ping sasha.stanford.edu
timv@timv-5510:~$ ping sasha.stanford.edu
PING sasha.stanford.edu (171.64.160.16) 56(84) bytes of data.
PING sasha.stanford.edu (171.64.160.16) 56(84) bytes of data.
64 bytes from sasha.stanford.edu (171.64.160.16): icmp_seq=1 ttl=48 time=29.7 ms
64 bytes from sasha.stanford.edu (171.64.160.16): icmp_seq=1 ttl=48 time=29.7 ms
64 bytes from sasha.stanford.edu (171.64.160.16): icmp_seq=2 ttl=48 time=29.7 ms
64 bytes from sasha.stanford.edu (171.64.160.16): icmp_seq=2 ttl=48 time=29.7 ms
From LA, I get 29.7ms round trip ping time to the cluster. This is quite respectable. Less than 100ms is quite good, and 15ms is about the limit of human perception.
From LA, I get 29.7ms round trip ping time to the cluster. This is quite respectable. Less than 100ms is quite good, and 15ms is about the limit of human perception.
==Connecting to a VM==
If you'd like to connect from off-campus, you need to use the [https://uit.stanford.edu/service/vpn Stanford VPN]. Stanford uses a Cisco AnyConnect VPN, which is available for Mac, Windows, and Linux clients. You can opt to use the "split-tunnel" VPN, which will only redirect Stanford traffic through the tunnel.
You also need a Remote Desktop client. On Windows, this is pre-installed. Just look for "Remote Desktop Connection." On Mac, you need to install [https://apps.apple.com/us/app/microsoft-remote-desktop/id1295203466 Microsoft Remote Desktop] from the Mac App Store. On Linux, there are several RDP clients available.
Join the #windows Slack channel for more info on how to get connected. When you use an instance, post a message in the channel when you start and finish so that others don't try to use the same machine simultaneously.
==Available VMs==
{|class="wikitable"
|ssi-ws1.stanford.edu
|Active
|-
|ssi-ws2.stanford.edu
|Active
|-
|ssi-ws3.stanford.edu
|Active
|-
|ssi-ws4.stanford.edu
|Active
|}