On Dec 17, Christoph Biardzki wrote:> I tried 0-config mounting today using the mount command - this also > works fine but portals debug stays enabled. Any ideas how to automate > this / how to disable debug by default?If you add this to your modules.conf, it should automatically get reset after module load: post-install portals sysctl -w portals.debug=0x3f0400 You can, of course, substitute any more debug value you choose; that one is a good mix of "some information for diagnosing problems" and "not so much as to materially hurt performance". Mike
Hi Christoph-- Christoph Biardzki wrote:> > disabling portals debug helps! Now I can see ~70 MB/s write througput > from one client to one server (equipped with a four-disk RAID0 which > achives around 100 MB/s write / 80 MB/s read for a 32 GB file). This is > pretty good!Not bad, although there is still an unusual bottleneck somewhere. Which benchmark are you using? If you run vmstat on the OSS and client, are you CPU-bound?> I tried 0-config mounting today using the mount command - this also > works fine but portals debug stays enabled. Any ideas how to automate > this / how to disable debug by default?The Lustre 1.0.2 release will have a more sensible default debugging level. Can you wait a week or so? Otherwise I think you would have to write a small script that sets the debug level afterwards with sysctl.> BTW: I just tried the current CVS version - works, but metadata > performance is horrible (~1 file create/s) - is there a reason or some > other hidden option? :))It is very difficult to choose the correct version of the code from CVS, so we strongly discourage people from trying. Nevertheless, 1 create/s is not normal. Do you have the same problem with the 1.0.1 packages? How are you creating these files? Thanks-- -Phil
Hello, disabling portals debug helps! Now I can see ~70 MB/s write througput from one client to one server (equipped with a four-disk RAID0 which achives around 100 MB/s write / 80 MB/s read for a 32 GB file). This is pretty good! I tried 0-config mounting today using the mount command - this also works fine but portals debug stays enabled. Any ideas how to automate this / how to disable debug by default? Regards, Christoph BTW: I just tried the current CVS version - works, but metadata performance is horrible (~1 file create/s) - is there a reason or some other hidden option? :)) -- Leibniz Rechenzentrum München (LRZ) http://www.lrz.de High Performance Systems Division Barer Str. 21 - 80333 Munich - Germany Tel. ++49-(0)89 / 289-28853, Room 1527