So after some more experimentation yesterday, moving 15 GB files and such, the 
lustre performance is fine.

It seems that the slow down occurs when a single file is being written in many 
chunks, and not related to security at all.  Could this be due to file locking? 
 Is there a good way to debug this?

Sincerely,


Don Kolva, PE, MCP
Director of Product Development
Accelerated Technology Laboratories, Inc.

Toll-free (US and Canada): 800-565-LIMS (5467)
Phone: 910-673-8165
Fax: 910-673-8166
www.atlab.com<http://www.atlab.com/>

"Innovation. Performance. Success."

[Description: cid:[email protected]]

From: [email protected] 
[mailto:[email protected]] On Behalf Of Donald J. Kolva
Sent: Monday, September 12, 2011 10:22 AM
To: [email protected]
Subject: [Lustre-discuss] Slow lustre after NIS

Lustre was as fast (or faster) than a local drive when security was handled by 
local nodes on a cluster.  Switching the cluster to NIS (and also switching the 
MDS to the same NIS server) seems to have made Lustre 5x slower.  Switching 
back to "local" security does not restore the speed.

Can Lustre work with NIS?  Does each OST need to be NIS or just the MDS?

Is there a good way to debug the performance of Lustre?  I've poured over the 
manual, but it doesn't seem clear on how to debug this performance problem.

Lustre over the 1 GB network is as slow as Infiniband.

Setup is on MDS, and three OST each running CentOS 5.5
Cluster is one headnode and 8 computenodes with RHEL 5.5

Thanks for any help!

<<image001.jpg>>

_______________________________________________
Lustre-discuss mailing list
[email protected]
http://lists.lustre.org/mailman/listinfo/lustre-discuss

Reply via email to