...
We have seen from time to time loads of the headnode resulting from jobs that should be directed to the compute nodes. Often this is just a user mistake, but results in lower quality of service to others trying to prepare work for the compute nodes. It is policy that all significant research codes and related work be submitted to run on the compute nodes. In order to help promote the best possible quality of service, effective 6-24-2013, any running jobs on the head node deemed load producing and excessive will be terminated without notice. This will help insure the best possible responsiveness of headnode resources for everyone. Offending users will be further notified and reminded to submit jobs to the compute nodes. Jobs are submitted with slurm commands to the appropriate slurm partition meeting your needs. If you any questions about this change, please send your comments via email to: clustertts-support@tuftsresearch@tufts.edu.
Application Xwindow QoS
Any application, such as Matlab, that creates interactive Xwindows gui presentations will often not display on your local xserver(cygwin, exceed, xwin32,etc...) with the same low latency associated with the application(Matlab) locally installed. This is partly a function of load on the compute node the application is running on, the denseness of the graphics you are creating, the load on the network that connects you remotely and the quality of your video card. It this presents an issue for development tasks, then a locally installed version of the application is suggested. The use of the cluster thereafter could be in support of batch processing to achieve some desired level of scaling. If you any questions, please send your comments to: cluster-support@tufts.edu.
...