| ... | @@ -45,7 +45,7 @@ Results (everything the code prints) are saved in file `outputfile`. For more de |
... | @@ -45,7 +45,7 @@ Results (everything the code prints) are saved in file `outputfile`. For more de |
|
|
## kone
|
|
## kone
|
|
|
kone (connect: `ssh kone.phys.jyu.fi` within the JYU network/VPN) is a small Linux machine running RedHat 8 with $\mathcal{O}(60)$ CPUs. It is somewhat old (CPUs from 2019). It is a single machine with no queue system.
|
|
kone (connect: `ssh kone.phys.jyu.fi` within the JYU network/VPN) is a small Linux machine running RedHat 8 with $\mathcal{O}(60)$ CPUs. It is somewhat old (CPUs from 2019). It is a single machine with no queue system.
|
|
|
|
|
|
|
|
* Can be used for small interactive runs (for longer runs use e.g. [screen] to make sure that your program keeps running if you close the ssh connection)
|
|
* Can be used for small interactive runs (for longer runs use e.g. [`screen`](https://www.geeksforgeeks.org/screen-command-in-linux-with-examples/) to make sure that your program keeps running if you close the ssh connection)
|
|
|
* Make sure your program does not take all resources. Use e.g. `top` to see if other people are running their codes and to see how many CPUs there are available. If the code runs for a long time, don't reserve majority of the CPUs
|
|
* Make sure your program does not take all resources. Use e.g. `top` to see if other people are running their codes and to see how many CPUs there are available. If the code runs for a long time, don't reserve majority of the CPUs
|
|
|
* Don't do any heavy disc read/write
|
|
* Don't do any heavy disc read/write
|
|
|
* The filesystem is your university home folder, the same you see from Windows machines
|
|
* The filesystem is your university home folder, the same you see from Windows machines
|
| ... | |
... | |
| ... | | ... | |