Thanks to Andreas for taking an hour out to talk with Jeff Squyres and
myself (Brock Palen) about the Lustre cluster filesystem on our
podcast www.rce-cast.com,
You can find the whole show at:
http://www.rce-cast.com/index.php/Podcast/rce-14-lustre-cluster-filesystem.html
Thanks again!
If
Dear list ,
I am doing pressure test for a new 10-OSS Lustre file system
using 70 client node. (each server has 10Gb Ethernet connection, each client
has 1Gb Ethernet connection, there are 3 OST on 3 RAID6 volulme for one OSS)
Each time, after about 4 hours,
Very nice.
15:54, what is Nagle ?
He didn't say anything about SNS, but changeLogs seems very promising!
On Mon, Aug 3, 2009 at 8:55 AM, Brock Palenbro...@umich.edu wrote:
Thanks to Andreas for taking an hour out to talk with Jeff Squyres and
myself (Brock Palen) about the Lustre cluster
http://en.wikipedia.org/wiki/Nagle%27s_algorithm
Looks like you intentionally hold up data to try to make fatter
payloads in packets so they are not 99% header/crc data. Sounds like
a way to make latency bad.
Brock Palen
www.umich.edu/~brockp
Center for Advanced Computing
bro...@umich.edu
eitherway, good job on the interview. Andres was a sport. try to
interview more Lustre developers :-)
On Mon, Aug 3, 2009 at 8:35 PM, Brock Palenbro...@umich.edu wrote:
http://en.wikipedia.org/wiki/Nagle%27s_algorithm
Looks like you intentionally hold up data to try to make fatter payloads
Yes, originally designed so multiple send() calls with small data have
a chance to be combined by TCP before being sent over the network --
improve behavior of applications doing small writes.
Setting tcp_nodelay disables Nagle, as the additional latency can hurt
some interactive session
Yes, it hold up any packet that is less than the size of the header, and
forwards multiple.
- Original Message -
From: Brock Palen [bro...@umich.edu]
Sent: 08/03/2009 08:35 PM AST
To: Mag Gam magaw...@gmail.com
Cc: lustre-discuss discuss lustre-discuss@lists.lustre.org
Subject: Re:
