What is the reason for I/O Throttling, when you have Diskeeper already running at Priority 2?
Priority is used by the system to assign CPU time. However, once a request goes into the I/O Queue it is satisfied on a first-come, first-served basis. I/O Throttling is what makes Diskeeper user-transparent while it is running. It causes Diskeeper to wait briefly before each I/O operation and to monitor the number of I/O operations it uses in comparison to total I/O operations on the system. If Diskeeper is doing more than 75% of the I/O operations, the wait time is decreased, if it is doing less than 75% of the I/O operations, the wait time is increased. This does not have anything to do with CPU usage. The Central Processing Unit (CPU) handles the interpretation and execution of instructions. The CPU holds the main memory storage, arithmetic unit and special registers. The CPU sends the I/O request to the I/O Processor. The I/O Processor handles the I/O to the disk and returns the output to the CPU. In the meantime, the CPU is handling requests from other users or other processes. When IO_THROTTLING is enabled, CPU usage actually increases as there are more calculations involved in deciding how long to wait between I/O's. However, this is normally not a consideration in system response time as NOIO_THROTTLING would be.
If this FAQ helped, please let us know. If you didn't find the answer to your question here please e-mail
|
