Hello all, I can launch my program in batch, using qsub and a small instance terminates fine and gives good results. When I scale up my problem, and it takes longer than about 5 minutes, it seems to end at about that time. I hope there is no time limit right? Another minor problem also occured once, when I got /var/spool/PBS/mom_priv/jobs/12681.acaad01.SC: line 5: 31151 Bus error /home/sels/projects/KUL/RhinoCeros/retime/Debug/retime 0 [sels@acano01 Debug]$ while writing a few files of between 10 and 100 MBytes. Would that be a problem?

This is the way I typically submit batch jobs:

qsub -l select=1:ncpus=40 rl-myjob

Ever since the Memorial Day weekend maintenance, jobs submitted this way have been running about 5 times slower than than they do on the login node. I traced the problem to ncpus values greater than 32. For example, on a small test that uses 64 threads and normally runs in under 30 seconds:

qsub -l select=1:ncpus=32 rl-myjob
# Finishes in about 24 seconds

qsub -l select=1:ncpus=33 rl-myjob
# Takes over 120 seconds

Hi,

FYI, I have VNC and XMing working 100%. With the posts on the forum it's dead easy to set up. XMing is slow over long distances (I am in South Africa, even with 4mbps ADSL the latency makes X almost unbearable).

VNC is slightly faster because it only sends screen updates, and has the added advantage of persistent sessions - if the nodes aren't bounced while you are offline, your desktop will still be as you left it when you disconnected VNC. For the "purists", XMing does full XServer rendering on your remote PC, which is quite nice, but has no session persistence.

MTL will be unavailable from: ~5pm PDT May 27th through 9am PDT May 31st 2011

Please plan accordingly.