135
edits
Changes
Jump to navigation
Jump to search
Line 6:
Line 6: − ```+ − + − + − + − + − ``` + + + + + + + + +
no edit summary
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
|}