On Sun, Jun 28, 2009 at 12:17:50PM +0100, Dave Love wrote:
> > and for disks run a smartctl test and see if a disk is showing
> > symtopms which might make it fail in future.
>
> What I typically see from smartd is alerts when one or more sectors has
> already gone bad, although that tends not to
On Thu, 2009-06-25 at 13:09 -0500, Rahul Nabar wrote:
> On Tue, Jun 2, 2009 at 12:39 PM, Ashley Pittman
> wrote:
> Fdupes scans the filesystem looking for files where the size
> matches, if
> it does it md5's them checking for matches and if that matches
> it
>
Dave Love wrote:
Rahul Nabar writes:
What are typical latencies I ought to be seeing with gigabit eth?
I have some data at http://www.nw-grid.ac.uk/LivMPI
Note that you may have to tune the driver parameters to get the lowest
latency.
Dave,
Can you say something about any tuning you did t
Rahul Nabar writes:
> What are typical latencies I ought to be seeing with gigabit eth?
I have some data at http://www.nw-grid.ac.uk/LivMPI
Note that you may have to tune the driver parameters to get the lowest
latency.
___
Beowulf mailing list, Beowu
Rahul Nabar writes:
> On Fri, Jun 26, 2009 at 1:30 PM, Jeff Layton wrote:
>> Try something like OpenMX over GigE. Much better latencies
∼6μs, if that counts as much better.
>> and should perform and scale better.
Are there data on that? I'm not clear how much more efficient than TCP
it might
Prentice Bisbal writes:
>> Will there be any performance loss (or gain) in compiling the fortran77
>> code with mpif90 (where the code will be containing some fortran90
>> constructs as well)? Any opinion?
>
> I doubt it. Most modern Fortran compilers do F77 and F90 (ifort and
> gfortran for exam
"Douglas Eadline" writes:
> As far as HPC, Erlang is interpreted although it can be "compiled"
Surely it's normally compiled, whether to byte code or not.
Although you don't want to be doing serious numerical work in it
directly, I guess there's nothing fundamental to prevent it being
compiled
Marian Marinov writes:
> It is really strange but in a good way :) Combining ideas of different
> programming languages.
I'm not sure what that refers to, but I think the strangest thing about
it is the Prolog-y syntax. At least the Actor-like model should be
familiar from MPI, though Erlang st
John Hearns writes:
> However, you could look of correctable ECC errors,
On the systems with which I'm familiar, they either won't show up in the
IPMI SEL or will apparently be inconsistent with the kernel mcelog --
mcelog typically displays many more events. (I don't know why this is,
though I
