search for: ldlm_poold

Hi, I''m seeing what can only be described as dismal striped write performance from lustre 1.6.3 clients :-/ 1.6.2 and 1.6.1 clients are fine. 1.6.4rc3 clients (from cvs a couple of days ago) are also terrible. the below shows that the OS (centos4.5/5) or fabric (gigE/IB) or lustre version on the servers doesn''t matter - the problem is with the 1.6.3 and 1.6.4rc3 client kernels

...tre-1.6.3 and we are seeing some pretty poor performance with most of the mpiblast threads spending 20% to 50% of their time in disk wait. We have the genbank nt database split into 24 fragments (one for each of our OSTs, 3 per OSS). The individual fragments are not striped due to the ldlm_poold issue so that should not be the problem. Should we not be using the PIO (ROM-IO) version of MPIBlast w/ lustre? I''m wondering if there are some already discovered guidelines for using MPIBlast on top of Lustre that I''m not finding via google. Thanks, Charlie Taylor UF HPC...