On 2010-03-04, at 14:18, Jeffrey Bennett wrote:
I just noticed the sequential performance is ok, but the random IO
(which is what I am measuring) is not. Is there any way to increase
random IO performance on Lustre? We have LUNs that can provide
around 250.000 random read 4kb IOPS but we
On 2010-03-04, at 05:46, Frederik Ferner wrote:
Brian J. Murrell wrote:
On Thu, 2010-03-04 at 11:21 +, Frederik Ferner wrote:
tar tizf test_MDT_Backup.tar.gz
./ROOT/tmp/frederik/cs04r-sc-com02-04/
./ROOT/tmp/frederik/cs04r-sc-com02-04/iozone.DUMMY.47
tar: Unexpected EOF in archive
Hi everyone,
I have a critical problem on one of my Lustre client machines running
Scientific Linux 5.4 and the patchless Lustre 1.8.2 client. After a
few days of usage, some processes like cp and kswapd0 start to use
100% CPU. Only 180k of swap space are in use though.
Processes that try to
Hi Guys,
How does lustre handle locking? One of our users is complaining that a perl
module (Sotrable) has trouble with its lock_nstore method when it tries to
use flock. The following is a hwo they are reporducing this issue:
--
perl -d -e ''
Loading DB routines from perl5db.pl version 1.3
Andreas, if we are using 4kb blocks I understand we only transfer 1 page per
RPC call, so are we limited to 10-15K RPC per second or what's the same,
10-15.000 IOPS?
jab
-Original Message-
From: andreas.dil...@sun.com [mailto:andreas.dil...@sun.com] On Behalf Of
Andreas Dilger
Sent:
On 2010-03-05, at 14:49, Jagga Soorma wrote:
How does lustre handle locking? One of our users is complaining
that a perl module (Sotrable) has trouble with its lock_nstore
method when it tries to use flock. The following is a hwo they are
reporducing this issue:
DB6 flock(FOO,
On 2010-03-05, at 14:53, Jeffrey Bennett wrote:
Andreas, if we are using 4kb blocks I understand we only transfer 1
page per RPC call, so are we limited to 10-15K RPC per second or
what's the same, 10-15.000 IOPS?
That depends on whether you are doing read or write requests, whether
it
Hi Guys,
Thanks Andreas for pointing me to the flock options. However, I see the
following caution statement for the consistent mode:
--
CAUTION: This mode has a noticeable performance impact and may affect
stability, depending on the Lustre version used. Consider using a newer
Lustre version
On 2010-03-05, at 15:18, Jagga Soorma wrote:
Thanks Andreas for pointing me to the flock options. However, I see
the following caution statement for the consistent mode:
--
CAUTION: This mode has a noticeable performance impact and may
affect stability, depending on the Lustre version
On Friday 05 March 2010, Götz Waschk wrote:
Hi everyone,
I have a critical problem on one of my Lustre client machines running
Scientific Linux 5.4 and the patchless Lustre 1.8.2 client. After a
few days of usage, some processes like cp and kswapd0 start to use
100% CPU. Only 180k of swap
Hello!
On Mar 5, 2010, at 5:25 PM, Andreas Dilger wrote:
On 2010-03-05, at 15:18, Jagga Soorma wrote:
Is there an impact if the option is turned on, or only if it is
turned on and used? Is the impact local to the file being locked,
the machine on which that file is locked, or the entire
11 matches
Mail list logo
