Hi Tim, I've just change the options and rdsm hasnt solved the problem. The behaviour is the same. Talking about memory, is not a limitation, and the procs are Xeon 54XX. The comparison gigabit vs infiniband is the following :
16 proc gigabit -> 2'
16 proc infi -> 20"'
32 proc gigabit -> 4'
32 proc infi -> 5'20"
Do you think I should change the forum ? Is there any var I could use or anything I could test to improve the performance ?
Thanks
PD. This is the top in a node when we launch 32 proc :
Cpu0 : 20.7%us, 79.3%sy, 0.0%ni, 0.0%id, 0.0%wa, 0.0%hi, 0.0%si, 0.0%st
Cpu1 : 0.0%us,100.0%sy, 0.0%ni, 0.0%id, 0.0%wa, 0.0%hi, 0.0%si, 0.0%st
Cpu2 : 0.3%us, 99.7%sy, 0.0%ni, 0.0%id, 0.0%wa, 0.0%hi, 0.0%si, 0.0%st
Cpu3 : 0.3%us, 99.7%sy, 0.0%ni, 0.0%id, 0.0%wa, 0.0%hi, 0.0%si, 0.0%st
Cpu4 : 0.3%us, 99.7%sy, 0.0%ni, 0.0%id, 0.0%wa, 0.0%hi, 0.0%si, 0.0%st
Cpu5 : 3.0%us, 97.0%sy, 0.0%ni, 0.0%id, 0.0%wa, 0.0%hi, 0.0%si, 0.0%st
Cpu6 : 49.5%us, 50.5%sy, 0.0%ni, 0.0%id, 0.0%wa, 0.0%hi, 0.0%si, 0.0%st
Cpu7 : 17.0%us, 83.0%sy, 0.0%ni, 0.0%id, 0.0%wa, 0.0%hi, 0.0%si, 0.0%st
Mem: 8170628k total, 1038224k used, 7132404k free, 246276k buffers
Swap: 1020116k total, 0k used, 1020116k free, 352364k cached
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
6853 caton2 25 0 77456 33m 5624 R 100 0.4 17:00.01 mm5.mpp
6854 caton2 25 0 78664 34m 5880 S 100 0.4 16:59.99 mm5.mpp
6855 caton2 25 0 78212 34m 5764 S 100 0.4 16:59.23 mm5.mpp
6852 caton2 25 0 77388 33m 5224 S 100 0.4 16:59.95 mm5.mpp
6856 caton2 25 0 79232 34m 6068 R 100 0.4 16:58.75 mm5.mpp
6857 caton2 25 0 78152 34m 5800 R 100 0.4 17:00.00 mm5.mpp
6858 caton2 25 0 77620 33m 5684 S 100 0.4 16:59.99 mm5.mpp
6859 caton2 25 0 77268 33m 5136 R 100 0.4 16:59.71 mm5.mpp
As you can see, CPU0,6,7 are running user proc, while the CPU1,2,3,4,5 are always busy with the system ones. Always is the samen situation. Is there anyway to get down the system ones at CPU1,2,3,4,5 ?