Skip to main content
deleted 3 characters in body
Source Link
Indrek
  • 24.6k
  • 14
  • 91
  • 93

Intelligently choosing the percentages for Windows power options, then, involves in finding out which P-states your processor supports, deciding the minimum and maximum clock speeds you wish to use and then entering the percentages that result in those clock speeds. There's no single correct answer as everything depends on your goals - whether you want to maximise performance or battery life, reduce temperatures or something else entirely. Experiment and see what works out best for you. Personally I've found that setting minimum and maximum to 5% (low enough to force lowest multiplier regardless of processor) and 100%, respectively, gives the best results. Yes, even on battery. While it might seem logical to set maximum processor state to less than 100% on battery, in my experience it's better to have the processor spend some time in the highest P-state and then return to idle as fast as possible, than to have it spend more time in some intermediate state.

Intelligently choosing the percentages for Windows power options, then, involves in finding out which P-states your processor supports, deciding the minimum and maximum clock speeds you wish to use and then entering the percentages that result in those clock speeds. There's no single correct answer as everything depends on your goals - whether you want to maximise performance or battery life, reduce temperatures or something else entirely. Experiment and see what works out best for you. Personally I've found that setting minimum and maximum to 5% (low enough to force lowest multiplier regardless of processor) and 100%, respectively, gives the best results. Yes, even on battery. While it might seem logical to set maximum processor state to less than 100% on battery, in my experience it's better to have the processor spend some time in the highest P-state and then return to idle as fast as possible, than to have it spend more time in some intermediate state.

Intelligently choosing the percentages for Windows power options, then, involves finding out which P-states your processor supports, deciding the minimum and maximum clock speeds you wish to use and then entering the percentages that result in those clock speeds. There's no single correct answer as everything depends on your goals - whether you want to maximise performance or battery life, reduce temperatures or something else entirely. Experiment and see what works out best for you. Personally I've found that setting minimum and maximum to 5% (low enough to force lowest multiplier regardless of processor) and 100%, respectively, gives the best results. Yes, even on battery. While it might seem logical to set maximum processor state to less than 100% on battery, in my experience it's better to have the processor spend some time in the highest P-state and then return to idle as fast as possible, than to have it spend more time in some intermediate state.

Bounty Ended with 100 reputation awarded by CommunityBot
added 218 characters in body
Source Link
Indrek
  • 24.6k
  • 14
  • 91
  • 93

The number of P-states supported varies by processor, but is usually around 5-10. Since Windows allows a total of 100 different values for the processor state, this means that not every value will result in a different P-state being used. In other words, going from 100% to 99% or even 90% might have no effect whatsoever on the clock speed. Also, depending on which P-states are supported, the actual clock speed might be differ considerably from what you might expect by quite a bit;from the percentage; specifying 50% in Windows power options doesn't necessarily mean that your processor will run at 50% clock speed. For instance, on my Core 2 Duo T9550 with a nominal clock speed of 2.66 GHz, setting the processor state to 50% doesn't give a clock speed of 1.33 GHz, as might be expected. Instead, Windows chooses the lowest supported multiplier (FID 6 6), which results in a clock speed of ~1.6 GHz (FSB 266 MHz × multiplier 6 = 1596 MHz). See, or 60% of the nominal clock speed, as evidenced by the image below:.2

Also, even if the minimum state is set to 1%, my processor won't go below ~800 MHz (SuperLFM), which is the lowest supported clock speed (FSB 133 MHz × multiplier 6 = 798 MHz); this corresponds tois 30% in Windows power optionsof the nominal clock speed.

Intelligently choosing the percentages for Windows power options, then, involves in finding out which P-states your processor supports, deciding the minimum and maximum clock speeds you wish to use and then entering the percentages that result in those clock speeds. There's no single correct answer as everything depends on your goals - whether you want to maximise performance or battery life, reduce temperatures or something else entirely. Experiment and see what works out best for you. Personally I've found that setting minimum and maximum to 5% (low enough to force lowest multiplier regardless of processor) and 100%, respectively, works outgives the best results. Yes, even on battery. While it might seem logical to set maximum processor state to less than 100% on battery, in my experience it's better to have the processor spend some time in the highest P-state and then return to idle as fast as possible, than to have it spend more time in some intermediate state.

The number of P-states supported varies by processor, but is usually around 5-10. Since Windows allows a total of 100 different values for the processor state, this means that not every value will result in a different P-state being used. In other words, going from 100% to 99% or even 90% might have no effect whatsoever on the clock speed. Also, depending on which P-states are supported, the actual clock speed might be differ from what you might expect by quite a bit; specifying 50% in Windows power options doesn't necessarily mean that your processor will run at 50% clock speed. For instance, on my Core 2 Duo T9550 with a nominal clock speed of 2.66 GHz, setting the processor state to 50% doesn't give a clock speed of 1.33 GHz, as might be expected. Instead, Windows chooses the lowest supported multiplier (FID 6), which results in a clock speed of ~1.6 GHz (FSB 266 MHz × multiplier 6 = 1596 MHz). See the image below:2

Also, even if the minimum state is set to 1%, my processor won't go below ~800 MHz (SuperLFM), which is the lowest supported clock speed (FSB 133 MHz × multiplier 6 = 798 MHz); this corresponds to 30% in Windows power options.

Intelligently choosing the percentages for Windows power options, then, involves in finding out which P-states your processor supports, deciding the minimum and maximum clock speeds you wish to use and then entering the percentages that result in those clock speeds. There's no single correct answer as everything depends on your goals - whether you want to maximise performance or battery life, reduce temperatures or something else entirely. Experiment and see what works out best for you. Personally I've found that setting minimum and maximum to 5% (low enough to force lowest multiplier regardless of processor) and 100%, respectively, works out best. Yes, even on battery. While it might seem logical to set maximum processor state to less than 100% on battery, in my experience it's better to have the processor spend some time in the highest P-state and then return to idle as fast as possible, than to have it spend more time in some intermediate state.

The number of P-states supported varies by processor, but is usually around 5-10. Since Windows allows a total of 100 different values for the processor state, this means that not every value will result in a different P-state being used. In other words, going from 100% to 99% or even 90% might have no effect whatsoever on the clock speed. Also, depending on which P-states are supported, the actual clock speed might differ considerably from what you might expect from the percentage; specifying 50% in Windows power options doesn't necessarily mean that your processor will run at 50% clock speed. For instance, on my Core 2 Duo T9550 with a nominal clock speed of 2.66 GHz, setting the processor state to 50% doesn't give a clock speed of 1.33 GHz, as might be expected. Instead, Windows chooses the lowest supported multiplier (FID 6), which results in a clock speed of ~1.6 GHz (FSB 266 MHz × multiplier 6 = 1596 MHz), or 60% of the nominal clock speed, as evidenced by the image below.2

Also, even if the minimum state is set to 1%, my processor won't go below ~800 MHz (SuperLFM), which is the lowest supported clock speed (FSB 133 MHz × multiplier 6 = 798 MHz); this is 30% of the nominal clock speed.

Intelligently choosing the percentages for Windows power options, then, involves in finding out which P-states your processor supports, deciding the minimum and maximum clock speeds you wish to use and then entering the percentages that result in those clock speeds. There's no single correct answer as everything depends on your goals - whether you want to maximise performance or battery life, reduce temperatures or something else entirely. Experiment and see what works out best for you. Personally I've found that setting minimum and maximum to 5% (low enough to force lowest multiplier regardless of processor) and 100%, respectively, gives the best results. Yes, even on battery. While it might seem logical to set maximum processor state to less than 100% on battery, in my experience it's better to have the processor spend some time in the highest P-state and then return to idle as fast as possible, than to have it spend more time in some intermediate state.

added 218 characters in body
Source Link
Indrek
  • 24.6k
  • 14
  • 91
  • 93

The number of P-states supported varies by processor, but is usually around 5-10. Since Windows allows a total of 100 different values for the processor state, this means that not every value will result in a different P-state being used. In other words, going from 100% to 99% or even 90% might have no effect whatsoever on the clock speed. Also, depending on which P-states are supported, the actual clock speed might be differ from what you might expect by quite a bit; specifying 50% in Windows power options doesn't necessarily mean that your processor will run at 50% clock speed. For instance, on my Core 2 Duo T9550 with a nominal clock speed of 2.66 GHz, setting the processor state to 50% doesn't give a clock speed of 1.33 GHz, as might be expected. Instead, Windows chooses the lowest supported multiplier (FID 6), which results in a clock speed of ~1.6 GHz (FSB 266 MHz × multiplier 6 = 1596 MHz). See the image below:2

The number of P-states supported varies by processor, but is usually around 5-10. Since Windows allows a total of 100 different values for the processor state, this means that not every value will result in a different P-state being used. In other words, specifying 50% in Windows power options doesn't necessarily mean that your processor will run at 50% clock speed. For instance, on my Core 2 Duo T9550 with a nominal clock speed of 2.66 GHz, setting the processor state to 50% doesn't give a clock speed of 1.33 GHz, as might be expected. Instead, Windows chooses the lowest supported multiplier (FID 6), which results in a clock speed of ~1.6 GHz (FSB 266 MHz × multiplier 6 = 1596 MHz). See the image below:2

The number of P-states supported varies by processor, but is usually around 5-10. Since Windows allows a total of 100 different values for the processor state, this means that not every value will result in a different P-state being used. In other words, going from 100% to 99% or even 90% might have no effect whatsoever on the clock speed. Also, depending on which P-states are supported, the actual clock speed might be differ from what you might expect by quite a bit; specifying 50% in Windows power options doesn't necessarily mean that your processor will run at 50% clock speed. For instance, on my Core 2 Duo T9550 with a nominal clock speed of 2.66 GHz, setting the processor state to 50% doesn't give a clock speed of 1.33 GHz, as might be expected. Instead, Windows chooses the lowest supported multiplier (FID 6), which results in a clock speed of ~1.6 GHz (FSB 266 MHz × multiplier 6 = 1596 MHz). See the image below:2

added 1537 characters in body
Source Link
Indrek
  • 24.6k
  • 14
  • 91
  • 93
Loading
added 1537 characters in body
Source Link
Indrek
  • 24.6k
  • 14
  • 91
  • 93
Loading
Source Link
Indrek
  • 24.6k
  • 14
  • 91
  • 93
Loading