Comments (1)
  • Add a Comment
  • Edit
  • More Actions v
  • Quarantine this Entry

1 localhost commented Permalink

I went through your suggestions and strategy, and found it confusing.<div>&nbsp;</div> First the exact command to check if the buffer needs tuning seems to be:<div>&nbsp;</div> vmstat -v | grep -i "I/Os blocked with no fsbuf"<div>&nbsp;</div> Which lists three possible areas to check:2740 filesystem I/Os blocked with no fsbuf0 client filesystem I/Os blocked with no fsbuf495 external pager filesystem I/Os blocked with no fsbuf<div>&nbsp;</div> This command is incorrect:ioo -h j2_nBufferPerPagerDevices It should be:ioo -h j2_nBufferPerPagerDevice<div>&nbsp;</div> I am a little confused why you say that j2_nBufferPerPagerDevice is decpreciated but then reccomend setting it anyway.<div>&nbsp;</div> It looks like my system could be tuned, so here is what I did:&gt;vmstat -v | grep -i "I/Os blocked with no fsbuf"2740 filesystem I/Os blocked with no fsbuf0 client filesystem I/Os blocked with no fsbuf495 external pager filesystem I/Os blocked with no fsbuf<div>&nbsp;</div> &gt;ioo -a | grep j2_nBufferPerPagerDevicej2_nBufferPerPagerDevice = 512<div>&nbsp;</div> &gt;ioo -po j2_nBufferPerPagerDevice=2048Setting j2_nBufferPerPagerDevice to 2048 in nextboot fileSetting j2_nBufferPerPagerDevice to 2048Warning: the j2_nBufferPerPagerDevice change is only effective for future mounts<div>&nbsp;</div> &gt;ioo -a | grep -i j2_dynamicBufferPreallocationj2_dynamicBufferPreallocation = 16<div>&nbsp;</div> &gt;ioo -po j2_dynamicBufferPreallocation=32Setting j2_dynamicBufferPreallocation to 32 in nextboot fileSetting j2_dynamicBufferPreallocation to 32<div>&nbsp;</div> <div>&nbsp;</div> <div>&nbsp;</div> <div>&nbsp;</div> <div>&nbsp;</div>