Jump to content
IObit Forum
Top Free Driver Updater Tools Best 25 PC Optimization Software Best 22 Antimalware Best 22 Uninstaller Software IObit Coupons & Discount Offers PC Optimizer Mac Boost Advice IObit Coupons A Good Utility Program From IObit IObit Promo Codes IObit Coupon Codes IObit Coupons and Deals FAQs Driver Booster Pro Review

GUI layout, and too large IO requests with slow response

Recommended Posts

Also, several static captions in the GUI are extremely short, and cannot adapt themselves to the effective string length.

The screen should have a more dynamic layout, allowing it to fit on larger (or smaller) screens.


Also, why does your program display the color-coded allocation grid using external images? Can't this grid just be made adjustable to the screen? (Note that I've still been unable to see any use of the orange cell.



And the program is really too long to stop if it is handling very large files: your program should try moving very large files by successive segments of smaller sizes (about 64MB max in the IO completion list should be enough to still benefit of maximum disk bandwidth and low numer of IO requests). This is a problem when IOSD tried to defragment some files that are 1GB or more (such as backup archive files, or older, non-active system snapshot and restoration files, or databases, or desktop search engine indexes)


This makes the program not very smart enuogh for use immediately with other disk intensive applications, and enabling the Smart background defragmenter is too risky.


Note also that this causes another problem: you may ask to IOSD to stop, then you'll think it has stopped because the disk is apparently not active (or has very low activity). However the CPU usage for some internal thread is still high, waiting for completion and apparently never completing.

You can click on "Quit" in the System Tray, and you'll think it is no longer running. However the proces will still be there.


If you relaunch it from the desktop icon or start menu, it will start a new process. In other words, the IOSD processes are accumulating over time.

(The process also survices when I close the session, most probably because it is still owning a IO Request completion queue, and still refuses to quit as long as the termination event does not come).


When rebooting, it takes infinite time to close the program, then it is killed abruptly by the OS. Quite dangerous for a disk utility to depend on the brutal termination of its process. Really, such tool MUST be able to complete ALL its IO requests in a reasonnable time.


So think about reducing/limiting the data size of your IO completion queues!

Link to comment
Share on other sites


This topic is now archived and is closed to further replies.

  • Create New...