- Joined
- Apr 2, 2007
- Messages
- 618
- Reaction score
- 73
- Points
- 0
- Location
- Oslo, Norway
- Website
- www.basefarm.no
Hi,
Just a little tip to get more IO from your system. If you have a raid subsystem or san, you can benefit a lot by setting the right scheduler for your disk queue.
As root (of course)
Goto this directory:
cd /sys/block
Get a list of how things are looking. You will see some settings (noop anticipatory deadline cfq) where cfq will most likely be in [].
grep '' */queue/scheduler
Google these words to find what the do.
My setting was to set them all to noop
This is done by
echo noop > /sys/block/sda/queue/scheduler
Do this for all your tsm mount points (replace sda with sdb)
These settings will not survive a reboot. So you can make a file that TSM runs before it starts up, or add it to the kernel startup with elevator=noop on the kernel line.
Just a little tip to get more IO from your system. If you have a raid subsystem or san, you can benefit a lot by setting the right scheduler for your disk queue.
As root (of course)
Goto this directory:
cd /sys/block
Get a list of how things are looking. You will see some settings (noop anticipatory deadline cfq) where cfq will most likely be in [].
grep '' */queue/scheduler
Google these words to find what the do.
My setting was to set them all to noop
This is done by
echo noop > /sys/block/sda/queue/scheduler
Do this for all your tsm mount points (replace sda with sdb)
These settings will not survive a reboot. So you can make a file that TSM runs before it starts up, or add it to the kernel startup with elevator=noop on the kernel line.
