Adding I/O Prioritization Settings to MyDefrag?

[Digital Parasite]

Right now you can configure MyDefrag to run at a lower process priority by using the SlowDown() command (http://www.mydefrag.com/FAQUsing-HowToRunWithALowerPriority.html).

In Vista and Windows 7, Microsoft has added another useful feature called I/O Prioritization where you can set the I/O priority of an application.  This would allow you to run something like a SlowOptimize that takes a long time in the background without affecting your regular usage since other I/O tasks would get higher priority if you set it low.  Good anti-virus programs do this so they don't bog down your system while a scan is running.

Would it be possible to add support for setting I/O prioritization?  You could add something like a SlowDownIO() command for those of us running a supported OS.  The necessary technical details are here:  http://www.microsoft.com/whdc/driver/priorityio.mspx

Thanks,
DP

[jeroen]

Thanks for sharing your idea, I appreciate it. I already have it on my wishlist to add something like that to MyDefrag.

[poutnik]

Note that if JkDefrag is used with task scheduler in vista,
it automatically decreases both process and I/O priorities.

I have not tried scheduled MyDefrag yet,
but I suppose it will be the same,
as far as I have noticed it as a default behavior for user scheduled tasks.

[Digital Parasite]

Note that if JkDefrag is used with task scheduler in vista,
it automatically decreases both process and I/O priorities.

I have not tried scheduled MyDefrag yet,
but I suppose it will be the same,
as far as I have noticed it as a default behavior for user scheduled tasks.

With Vista 64bit this does not seem to be the case with MyDefrag.  Right now I have Fast Update running through Task Scheduler.  It's process priority is set to "Below Normal" but its I/O priority is still "Normal".

DP

[poutnik]

With Vista 64bit this does not seem to be the case with MyDefrag.  Right now I have Fast Update running through Task Scheduler.  It's process priority is set to "Below Normal" but its I/O priority is still "Normal".

Well, on my vista 64 Home Premium JKDefrag run with lowered IO priority, without my any intervention.

[peters40]

On my system Vista 64 bit

    Run from script       Normal priorty 8
    Run from Task Sch  Below Normal 6

[Digital Parasite]

On my system Vista 64 bit

    Run from script       Normal priorty 8
    Run from Task Sch  Below Normal 6

We are talking about I/O priority, not process priority, so I just wanted to make sure that is what you are reporting?  You need a program like Sysinternal's Process Explorer in order to see the I/O priority value.  You can do this by finding the process in Process Explorer, right clicking on the process, selecting Properties and then clicking on the "Performance" tab.  You can see both the CPU Priority and I/O Priority listed.

[Digital Parasite]

Well, on my vista 64 Home Premium JKDefrag run with lowered IO priority, without my any intervention.

Yes, you said that already.  I haven't tried JKDefrag, but MyDrag is behaving differently on my system.  What tool are you using to see IO priority?

DP

[peters40]

Vista 64  MyDefrag (FastOptimize)  Run from Task Sch     
                                          Set priority Below Normal 6
                                          I/0 priority Low
                                          Memory priority 3

[poutnik]

Looks like my data from Process Explorer....

[Digital Parasite]

I just checked on another Vista machine, this one is 32bit and I see the same behaviour is my Vista 64bit machine.  Now both of them are Vista Business editions.  I have attached a screen shot of FastUpdate being run from task scheduler.

On both systems I get:
Run from Task Sch     
Priority: Below Normal 6
I/0 priority: Normal
Memory priority: 5

So for some reason we are seeing different behaviour.  Could this be a Vista Business difference.  Or the fact that you guys are using FastOptimize instead of FastUpdate?

[poutnik]

So, now I have confirmed myself on my home PC  with Vista64 HPremium SP2 this:

if my custom MyD script for MyDefrag412 is scheduled on Task scheduler under SYSTEM account, and launched manually ( not yet checked the scheduled launch ),

it runs under Low I/O priority. so, it seems to be vista version dependent.

[Digital Parasite]

So, now I have confirmed myself on my home PC  with Vista64 HPremium SP2 this:

if my custom MyD script for MyDefrag412 is scheduled on Task scheduler under SYSTEM account, and launched manually ( not yet checked the scheduled launch ),

it runs under Low I/O priority. so, it seems to be vista version dependent.

Can you tell me exactly how you have your Task configured?  Mine was set to run under my user account.  When I change it to "SYSTEM" and launch it manually, Process Explorer can only read its process priority but not its IO or Memory priority they just show up as blank.  What does your "General" and "Actions" tab look like?

For Actions I'm just calling:  "C:\Program Files\MyDefrag v4.1.2\Scripts\FastOptimize.MyD"

For General I have tried both:
When running the task, use the following user account:
me
Run only when user is logged on

SYSTEM
Run whether use is logged on or not.

The first gives me Normal IO priority, the second doesn't let me read the IO priority.

[peters40]

Vista Ultimate
Task "C:\Program Files\MyDefrag v4.1.2\Scripts\FastOptimize.MyD"
Running admin account whever user logged on or not

I think the difference is "running under admin account logged on or not" , when task is running im logged on as ordinary user account

If i run from script  Normal IO priority, Memory 5

[poutnik]

Did you try to set Process Explorer to "Show all processes"  ?
I am used tu run it in this mode all the time.

At my PC  I am forced to run privilaged scheduled tasks under SYSTEM account.
Home Vista versions have a stupid "feature" they do not remember permanently provided passwords, if task is to be run under different credentials.

I use Vista as regular user, so I need to run scheduled tasks as SYSTEM,
where no password is needed ( if scheduler itself was run under admin privilege to set it )

Then, in my case "if user is logged on or not" is senseless.     


-