Windows Remote VMs - Revision history

Elijahk: Info about the #windows Slack channel

2022-02-16T02:16:41Z

Info about the #windows Slack channel

← Older revision		Revision as of 02:16, 16 February 2022
Line 17:		Line 17:

	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.		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==		==Available VMs==

Flynnd: /* Connecting to a VM */

2021-10-05T21:43:41Z

Connecting to a VM

← Older revision		Revision as of 21:43, 5 October 2021
Line 27:		Line 27:
	\|-		\|-
	\|ssi-ws3.stanford.edu		\|ssi-ws3.stanford.edu
	\|~~Inactive (due to low demand)~~		\|Active
	\|-		\|-
	\|ssi-ws4.stanford.edu		\|ssi-ws4.stanford.edu
	\|~~Inactive (due to low demand)~~		\|Active
	\|}		\|}

Timv at 01:41, 7 December 2020

2020-12-07T01:41:10Z

← Older revision		Revision as of 01:41, 7 December 2020
Line 24:		Line 24:
	\|-		\|-
	\|ssi-ws2.stanford.edu		\|ssi-ws2.stanford.edu
	\|Inactive		\|Active
			\|-
			\|ssi-ws3.stanford.edu
			\|Inactive (due to low demand)
			\|-
			\|ssi-ws4.stanford.edu
			\|Inactive (due to low demand)
	\|}		\|}

Timv at 23:22, 17 October 2020

2020-10-17T23:22:19Z

← Older revision		Revision as of 23:22, 17 October 2020
Line 13:		Line 13:
	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.

	==Available ~~Nodes~~==		==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.

			==Available VMs==
	{\|class="wikitable"		{\|class="wikitable"
	\|ssi-ws1.stanford.edu		\|ssi-ws1.stanford.edu

Timv at 23:13, 17 October 2020

2020-10-17T23:13:22Z

← Older revision		Revision as of 23:13, 17 October 2020
Line 1:		Line 1:
	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==

Timv: Timv moved page Remote Windows Workstations to Windows Remote VMs

2020-10-17T23:13:08Z

Timv moved page Remote Windows Workstations to Windows Remote VMs

← Older revision		Revision as of 23:13, 17 October 2020
(No difference)

Timv at 23:12, 17 October 2020

2020-10-17T23:12:25Z

← Older revision		Revision as of 23:12, 17 October 2020
Line 6:		Line 6:
	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.

			==Available Nodes==
			{\|class="wikitable"
			\|ssi-ws1.stanford.edu
			\|Active
			\|-
			\|ssi-ws2.stanford.edu
			\|Inactive
			\|}

Timv: Created page with "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. Thi..."

2020-10-17T23:08:23Z

Created page with "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. Thi..."

New page

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.

==Performance==
Sasha is a Dell 2U rackmount server, with a 16 core Ryzen EPYC CPU, and 16 RAM slots for DDR4. It's quite powerful, and is configured to run multiple VMs (effectively independent operating systems within a single computer). The system is ''oversubscribed'', meaning that each of the N systems can utilize far more than 1/N of the available resources. For non-interactive workloads (like Ansys) this means a remote VM will be significantly faster than a personal laptop.

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
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=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.