https://wikis.ch.cam.ac.uk/cuc3/wiki/index.php?action=history&feed=atom&title=Talk%3AMek-quake_Queueing_systemTalk:Mek-quake Queueing system - Revision history2026-04-13T04:02:05ZRevision history for this page on the wikiMediaWiki 1.39.7https://wikis.ch.cam.ac.uk/cuc3/wiki/index.php?title=Talk:Mek-quake_Queueing_system&diff=1491&oldid=previmport>Jra35 at 08:20, 22 June 20062006-06-22T08:20:29Z<p></p>
<table style="background-color: #fff; color: #202122;" data-mw="interface">
<col class="diff-marker" />
<col class="diff-content" />
<col class="diff-marker" />
<col class="diff-content" />
<tr class="diff-title" lang="en">
<td colspan="2" style="background-color: #fff; color: #202122; text-align: center;">← Older revision</td>
<td colspan="2" style="background-color: #fff; color: #202122; text-align: center;">Revision as of 08:20, 22 June 2006</td>
</tr><tr>
<td colspan="2" class="diff-lineno">Line 1:</td>
<td colspan="2" class="diff-lineno">Line 1:</td>
</tr>
<tr>
<td class="diff-marker" data-marker="−"></td>
<td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #ffe49c; vertical-align: top; white-space: pre-wrap;"><div>I don't know a lot about queuing systems, so I can only really talk about front-end problems. What has annoyed me about nimbus is that it is supposed to be for running parallel jobs, yet whenever I submit something (usually 2-10 but sometimes up to 20 nodes, which I have to run with 10 nodes, 2 jobs per node which is already not ideal) it can spend literally weeks in the queue while hundreds of serial jobs run. This leads me to use rama because I can get a job running sooner, however rama is not optimised for parallel work so although they start, they run very slowly and I no doubt annoy all the people wanting to run serial jobs there. Is there any way around this?</div></td>
<td colspan="2" class="diff-empty diff-side-added"></td>
</tr>
<tr>
<td class="diff-marker" data-marker="−"></td>
<td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #ffe49c; vertical-align: top; white-space: pre-wrap;"><br /></td>
<td colspan="2" class="diff-empty diff-side-added"></td>
</tr>
<tr>
<td class="diff-marker" data-marker="−"></td>
<td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #ffe49c; vertical-align: top; white-space: pre-wrap;"><div>Jane</div></td>
<td colspan="2" class="diff-empty diff-side-added"></td>
</tr>
</table>import>Jra35https://wikis.ch.cam.ac.uk/cuc3/wiki/index.php?title=Talk:Mek-quake_Queueing_system&diff=1490&oldid=previmport>Jra35 at 08:19, 22 June 20062006-06-22T08:19:35Z<p></p>
<p><b>New page</b></p><div>I don't know a lot about queuing systems, so I can only really talk about front-end problems. What has annoyed me about nimbus is that it is supposed to be for running parallel jobs, yet whenever I submit something (usually 2-10 but sometimes up to 20 nodes, which I have to run with 10 nodes, 2 jobs per node which is already not ideal) it can spend literally weeks in the queue while hundreds of serial jobs run. This leads me to use rama because I can get a job running sooner, however rama is not optimised for parallel work so although they start, they run very slowly and I no doubt annoy all the people wanting to run serial jobs there. Is there any way around this?<br />
<br />
Jane</div>import>Jra35