Is setting minimum processor state to 100% "harmful"

Speed addicts anonymous.

Moderator: Starfalcon

Is setting minimum processor state to 100% "harmful"

Postposted on Fri Jun 10, 2011 4:07 pm

I set the minimum processor state to 100%, It was shipped at 10%.
RAMBO
Gerbil Team Leader
 
Posts: 273
Joined: Sun May 01, 2011 11:34 am

Re: Is setting minimum processor state to 100% "harmful"

Postposted on Fri Jun 10, 2011 4:37 pm

Why would you want your CPU to run full bore 100% of the time? Thats just wasting power. Modern CPUs can essentially instantly ramp to meet your computing demands. Now, you won't harm your CPU running it at 100%, theres just no reason to actually do that.
Having twins has dramatically reduced the time I have to nerd out.
Corrado
Minister of Gerbil Affairs
 
Posts: 2568
Joined: Sun Feb 17, 2002 7:00 pm
Location: Gilbertsville, PA

Re: Is setting minimum processor state to 100% "harmful"

Postposted on Fri Jun 10, 2011 4:46 pm

If it's a laptop I'd leave it alone. If it's a desktop I use this rule of thumb. Did you notice the increased latency when you switched from CRT to LCD? If you did you may notice the sluggishness that comes from using speedstep and the like, as they often don't ramp up to full speed for your average tasks. Personally I'd leave it at max. For my sandybridge it's only a 15 watt difference anyways. Small price for the snappiness if you're the sort that would notice it.
Derfer
Gerbil
 
Posts: 80
Joined: Fri Oct 23, 2009 2:05 pm

Re: Is setting minimum processor state to 100% "harmful"

Postposted on Fri Jun 10, 2011 4:47 pm

Reasons I can think of for wanting to do that are:

1) You've got some piece of software that doesn't play nice with the CPU power management. For example, I have a system where Hulu videos stutter quite badly if CPU power management is enabled.

2) You're running a low-priority CPU-intensive background task like Folding@home, and want the CPU to run full-bore even though the background task isn't of high enough priority to kick the CPU out of power saving mode.

Reasons I can think of for *not* wanting to do that are:

1) It wastes power.

2) If your CPU cooling is marginal to begin with, it may shorten the life of the CPU.

Life is full of tradeoffs. If you're not doing either of the two things listed at the top of this post, then the reasons for *not* doing it probably take precedence. :wink:
(this space intentionally left blank)
just brew it!
Administrator
Gold subscriber
 
 
Posts: 37628
Joined: Tue Aug 20, 2002 10:51 pm
Location: Somewhere, having a beer


Return to Overclocking, Tweaking, & Cooling

Who is online

Users browsing this forum: No registered users and 1 guest