Bogdan Costescu wrote:
On Wed, 16 Jan 2008, Craig Tierney wrote:
Our queue limits are 8 hours.
...
Did that sysadmin who set 24 hour time limits ever analyze the amount
of lost computational time because of larger time limits?
While I agree with the idea and reasons of short job runtime limit
On Thu, Jan 17, 2008 at 02:53:36PM +0100, Bogdan Costescu wrote:
> On Wed, 16 Jan 2008, Craig Tierney wrote:
>
> >Our queue limits are 8 hours.
> >...
> >Did that sysadmin who set 24 hour time limits ever analyze the amount
> >of lost computational time because of larger time limits?
>
> While I
On Wed, 16 Jan 2008, Craig Tierney wrote:
Our queue limits are 8 hours.
...
Did that sysadmin who set 24 hour time limits ever analyze the amount
of lost computational time because of larger time limits?
While I agree with the idea and reasons of short job runtime limits, I
disagree with your
At 21:00 16.01.2008, Greg Lindahl <[EMAIL PROTECTED]> wrote:
Use an MPI which does this for you?
Two examples are InfiniPath MPI and OpenMPI.
.. and another is Scali MPI Connect. We do it in two dimensions;
latency or bandwidth policy, that is to use as few or many sockets as
possible. Once
Gerry Creager <[EMAIL PROTECTED]> writes:
> I'm constantly reminded of a meeting early on in the SCOOP project,
> which I participate in (http://scoop.sura.org). "We're able to
> virtualize our model applications using VMware and only see a 13%
> performance hit".
Oops. Please note that the VMwa
Craig Tierney <[EMAIL PROTECTED]> writes:
> Allowing users to run for days or weeks as SOP is begging for failure.
Define failure. Our time limit is typically somewhere around 5 or 6
days. Many codes don't have checkpointing, and it's often simply not
possible to add it because you don't have acc
