Existing users, log in.  New users, create a free account.  Lost password?

Mac OS X  |  System / Utilities  |  Tweaks / Enhancements  |  Renicer  |  Mainly good ...

Renicer

Renicer

graphical tool to automatically set cpu process priority

Version:  1.5

   [ Views: 1228 ]

Mainly good ...

Feedback Type:  Review

Contributed by: stickman67 Wednesday, April 27 2005 @ 03:10 AM PDT

Product Platform: MacOSX

Used Product For: Less than a month

Recommend Product: YES

I've been using both DBoost and Renicer, and both seem to give my old girl (B&W G3 with G4/500 CPU upgrade, OS X 10.3.9) at least a bit of a boost without necessarily turning it into a rocket.

And from the speed with which MS Word just opened tonight, when I gave the latest version of Renicer a try after using DBoost for a while (OK, I'm indecisive!), I think I'll be sticking with this app for now. There was definitely a bit of a zing happening.

A couple of minor gripes. First, I really think developers would be doing themselves a favour if they posted on VT what's changed in their latest version. It's not here, it doesn't seem to be on the developer's website, and it certainly ain't in the manual (still dated 2002 -- gripe no. 2!).

Otherwise, this seems to be a pretty solid little package. And according to my 60-second observation test using Cunning Fox (no, not very scientific, but what do you want for nothing?), Renicer uses only around 18 MB RAM, and between 0 and 4.1% CPU in the background, according to Cunning Fox. By comparison, DBoost uses 27 MB of RAM and up to 5.5% CPU in the background, and seems more busy in terms of CPU activity overall. OK, not huge differences, but differences nonetheless.   
Overall Rating:

Ease of Use:

Support:

Features:

Quality / Stability:

Price:

3 of 5 users found this helpful.

Rate this Review

Was this Review helpful? Yes | No

Comments

1 comments |

Corrections - stickman67

*Red face*

When I say I've been using DBoost and Renicer, I don't mean together. I've been using them alternately to try them out.

And apologies to the developer. The modification date on the manual is actually 1 March 2003. Still not good, but better than 2002.

Reply to This

Wednesday, April 27 2005 @ 03:14 AM PDT