DFO's io_limit, cpu_limit, process_limit and priority level

[Douglass Anderson]

I was running DFO, and called up HP about DFO running /continuously. I changed the IO_Limit but I was wondering what are "reasonable" settings for IO_limit CPU_limit, Process_limit, and priority levels for running DFO in the back ground? The Documentation says IO_Limit is "the maximum direct I/O rate (per second) of any one defragmentation process." that does not seem right it is set to 14 and using 200-600 io per second.

[comarow · Accepted solution]

There's a new version coming out soon. The cpu limit is the actual limit of cpu time, often consumed examining free space consolidation. It is supposed to be set it and forget it.

Remember some fragmentation is desireable as it finds small files spaces with less head travel than a perfectly contiguous disk.

I hope you have a support contract. The DFO group is very interested in real world results. Put it to my attention and we can work on bringing it to their attention.

[Douglass Anderson]

solved