Permanently change the processing priority of a running program with Prio

Prio is a simple program which adds a “Save Priority” option to Windows Task Manager effectively making any priority change by you permanent:

prio4

Screenshot originally found on the developer’s website

Of course this “Save Priority” feature is optional so you do not have to enable it (if you just want to change the processing priority for a limited amount of time).

In addition to the save priority feature, Prio has some other interesting tools just as “Silent Elevation” and adding useful tooltips to processes/service/connections in Windows Task Manager.

Now in terms of managing CPU usage Prio, only offering the ability to manually change CPU priority, is definitely inferior when compared to Process Tamer; however Prio is better for those people that prefer not to download programs like Process Tamer and rather prefer to use Windows Task Manager for their CPU usage management needs. You may download Prio from the following links:

***Prio is free for home use only

Click here to download Prio (32-bit)

Click here to download Prio (64-bit)

Share this post

Comments

Leave a Reply

Your email address will not be published. Required fields are marked *

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>

4 comments

  1. Ashraf
    Author/Mr. Boss

    @giovanni: You mean http://dottech.org/freewaresr/7015? =)

    Well Process Tamer is obviously the superior program in terms of managing CPU usage and changing priorities. Prio is just a simple program for those that don’t want to use programs like Process Tamer or AnVir Task Manager.

    @david roper: Hehe, nice story. Personally I never raise processing priority; rather I am one of those guys that only use these types of programs to lower them.

  2. david roper

    I seem to remember something like this in the old “1970-80″ days about priority levels and CPU cycles on a “large” 128k Digital Research computer. Big as a refrigerator – 128K. Something happened…

    It’s a good story for a Friday, so let me tell it. I’m old, indulge me.

    I remember changing a task to have a CPU level near the top of priorities – if not the absolute top. I mean that I wanted it to run and run without interference from anything else that anyone else might need.

    Well, it did it and – BAM! – I was in trouble because it exceeded the level of the system task of reading the keyboard and I was stuck in never-never land. Keyboard was non-responsive because it could never could get any cycles from the CPU. Nice mess, a Catch 22.

    I can’t remember how I got out the mess, I just remembered to be very careful about things like this. YMMV. ;-)