[lustre-discuss] LNET Self-test
paf at cray.com
Sun Feb 5 15:07:13 PST 2017
It seems to me that's not true any more, with larger RPC sizes available. Is there some reason that's not true?
From: lustre-discuss <lustre-discuss-bounces at lists.lustre.org> on behalf of Oucharek, Doug S <doug.s.oucharek at intel.com>
Sent: Sunday, February 5, 2017 3:18:10 PM
To: Jeff Johnson
Cc: lustre-discuss at lists.lustre.org
Subject: Re: [lustre-discuss] LNET Self-test
Yes, you can bump your concurrency. Size caps out at 1M because that is how LNet is setup to work. Going over 1M size would result in an unrealistic Lustre test.
> On Feb 5, 2017, at 11:55 AM, Jeff Johnson <jeff.johnson at aeoncomputing.com> wrote:
> Without seeing your entire command it is hard to say for sure but I would make sure your concurrency option is set to 8 for starters.
> Sent from my iPhone
>> On Feb 5, 2017, at 11:30, Jon Tegner <tegner at foi.se> wrote:
>> I'm trying to use lnet selftest to evaluate network performance on a test setup (only two machines). Using e.g., iperf or Netpipe I've managed to demonstrate the bandwidth of the underlying 10 Gbits/s network (and typically you reach the expected bandwidth as the packet size increases).
>> How can I do the same using lnet selftest (i.e., verifying the bandwidth of the underlying hardware)? My initial thought was to increase the I/O size, but it seems the maximum size one can use is "--size=1M".
>> lustre-discuss mailing list
>> lustre-discuss at lists.lustre.org
> lustre-discuss mailing list
> lustre-discuss at lists.lustre.org
lustre-discuss mailing list
lustre-discuss at lists.lustre.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the lustre-discuss