Enables Chill Boost feature, which reduces the CPU power state in specific circumstances to improve performance.

  This value is the number of times per second the chill boost updates. Higher values will increase responsiveness of the feature, but also can increase load on the CPU.

  This value is the number of times per second the chill boost settings panel updates. Because the settings panel does not run on the same timer as the feature itself, displayed values may not exactly match up with what is actually happening. Usually you would want the display panel updating slower, as it uses more resources and throws off its own results when running too quickly.

  The reservoir size is how many seconds your CPU is allowed to run at full load before Chill Boost kicks in, and should be matched to your CPU cooling system. For example, if you have a water cooled system that can't keep up with your overclock and it takes 30 seconds for your computer to crash at full load, you might want to set this at 10 seconds to limit unnecessary throttling but still prevent the system from reaching conditions in which it would crash. If you have an air-cooled system or a tight overclock, temperature issues can hit much faster so you might be better off leaving this value at 0. The reservoir only applies when looking at load. Temperature limit settings will ignore reservoir settings.

  The reservoir fill rate is a multiplier on how many seconds are filled per second of CPU underutilization. If you are overclocking your CPU in a configuration that is not thermally stable at 100% load, you might outpace your heat dissipation and crash if you set this value too high. If you are not overclocking, your CPU should be expected to handle 100% load just fine, in which case this feature would be more about improving heat, noise, and energy management at lower values.

  This is the CPU usage percentage at which the stressed power state limit is triggered. This is extra useful when temperature sensors are unavailable or when temperature sensors do not respond fast enough. This threshold works in conjunction with the boost reservoir.

  This is the temperature at which the stressed power state limit is triggered. This target ignores the boost reservoir and tries to reduce the CPU temperature until it is below the target. CPUs already have similar mechanisms built in. However, when overclocking these mechanisms tend to be disabled, save for some last-ditch temperature controls which tend to limit only clock speed and not voltage. Even when not overclocking, these features are typically nonconfigurable, so this setting gives you more flexibility to efficiently keep temperatures low and noise down without sacrificing performance under light loads.

  This should be higher than the Chill Boost Temperature Target. It works similarly, but can make more drastic voltage reductions by dropping to an even lower power state. If you are overclocking, this would be your last line of defense outside of built-in emergency thermal limiters which may wait to kick in until as much as 100C. While the default is 75C, I am not saying that 75C is safe, but it surely is a lot safer than a 100C hardware limiter. Depending on your hardware, if you are reaching 75C without overclocking, this may be evidence that your cooling system is inadequate, installed improperly, or failing.

  This setting reduces your temperature allowances based on load. When this setting is 5 and the load is 100%, the temperature target and critical limit will be reduced by 5. At 0% load, the reduction would be 0. This allows the tool to respond faster than by simply going by the temperature sensors alone. This setting can allow the CPU to bounce back to high performance quicker when load is reduced. The setting also enables the tool to catch temperature spikes quicker.

  Temperature sensors can be glitchy sometimes. This is a very basic protection mechanism which ignores negative temperature values coming from the temperature sensor. On my system, I was getting odd temperature spikes during load tests because the sensor was sending back negative numbers from time to time, causing my temperature protections to not work correctly.

  This setting is a power state limit for dealing with load or temperature under stressed conditions. Depending on your hardware, the optimum value for this setting may vary wildly. The auto-calibration feature will select the power state with the second highest voltage, which usually offers both high efficiency and decent performance, but you could use the information from the auto-calibration table to optimize this value yourself. Lower values should reach more conservative power states, but the power states follow a step function that varies by hardware, so you have to lower the value enough to reach the next step before any actual change happens.

  This setting is a power state limit for dealing with load or temperature under critical conditions. The value 0 will enable the maximum voltage drop available. Higher values may still be effective without reducing performance as much. Processors have their own built-in protection mechanisms, but this setting can offer another layer of protection, which can come in especially handy when overclocking as some hardware protection mechanisms may be disabled. Auto-calibration will always set this value to 0 for maximum safety, but depending on your hardware you may be able to select a higher value which is stable under constant maximum load, in which case I would recommend setting this to the most efficient power state shown in the auto-calibration table.

  The Chill Boost Safety Mechanism exists in case you are using Chill Boost to thermally stabilize an overclock, so that your system does not go full throttle and crash before Chill Boost is able to run. Chill Boost only functions correctly while the tool is running. This mechanism attempts to leave your computer in the reduced power state if the computer crashes until the tool is running again. This feature could potentially cause Chill Boost to limit power more often than intended. Also, with this setting enabled, your power plan will not be reverted back to your normal power plan when you exit Simplode Suite normally, so you might have poor performance when the tool is not running and not remember why. Many computers reset their power plan on restart for whatever reason, and this safety mechanism will not work correctly in this case, though you could lower the maximum CPU power state in the power plan to which your system reverts so that you can still have the same sort of protection.

  Chill Boost Efficiency Locker blocks background and low priority apps from switching your processor into performance mode. When a processor is in performance mode, efficiency losses can be enormous, leading to more heat, more noise, and possibly shorter device lifespans. We like performance, though, for things we are focused on, but often times a background process will put your device into performance mode unnecessarily. The heat can even reduce the performance of your foreground app, so this feature can even increase perceived performance.

  When the efficiency locker is enabled, this threshold determines when it is active. Other efficiency locker settings change specific aspects of this behavior, but in general the computer will be allowed to run at full throttle when the application you are currently focused on has at least one thread that is trying to use the CPU more than this threshold. Getting close to 100% thread load can be quite difficult because time spent waiting for resources does not count. With that in mind, you may need to keep this number unituitively low considering a thread at 60% load can still be starved for more processor power.

  Performance Optimized: In this mode, the feature will not engage until it has detected unnecessary boosting caused by background apps. Apps that you want to boost will be able to boost without delay.
Efficiency Optimized: In this mode, the feature will block boosting until it detects that an app that you want to boost needs boosting. This mode may delay boosting slightly.

  When enabled alongside the Chill Boost Efficiency Locker, it can more accurately detect when multithreaded apps have headroom for efficiency improvement. Sometimes multithreaded applications have exotic thread configurations which make it difficult to determine if they are facing a thread speed bottleneck. For applications where the total load is less than the thread load threshold, we can easily determine that we have room to increase efficiency. However, when total load is higher than the thread load threshold, threads could be cascading information to each other making them behave as a single thread with similar efficiency penalties, and if we judged simply be looking at the threads individually, we would incorrectly enter efficiency mode, noticeably reducing the performance of the app. By analyzing process CPU usage at small enough intervals, the tool is able to see moments when an app is completely caught up. The duration and cadence of these moments can be used to determine how much room we have for efficiency improvements without reducing performance even when threads are interacting in unknown ways.

  This is the threshold at which the Efficiency Locker Multithread Enhancement will consider the focused app busy enough to need maximum performance. To reduce the chance that a busy application may be throttled, the focus app will be considered busy from when it is triggered until the value falls below 0.5 if this threshold is above 0.5.

  When the Chill Boost Efficiency Locker activates, the max power state will be limited to this value. The default value of 99 is usually a substantial improvement in efficiency on its own, though the most efficient power state is likely lower than 99. The Auto Calibration feature can set this value to most efficient power state available. The efficiency locker may reduce the power state even lower than this setting depending on the other efficiency locker settings.

  The efficiency locker can sometimes cause unnecessary frame drops if it detects a brief period of favorable conditions. Higher values in this setting will increase the amount of time that the efficiency locker will wait before kicking in, reducing the chances that it will kick in at a bad time and cause a frame drop.

  These processes will only be allowed to run while the efficiency locker is active and not above the strict process energy state threshold. Use the file names of each process, separated by commas or new lines. While processes in the list are in the background and the maximum power state is above this value, they will be completely unresponsive. While processes in the list are in the foreground, the maximum power state will be limited to the threshold. This allows you to run selected processes at maximum efficiency while minimizing any negative impact on other foreground processes. There is no way to configure processes to run at different voltages simultaneously, so the only way to ensure efficiency for heavy background processes is to allow them to run only while the voltage is limited. Chill Boost Efficiency Locker offers the unique capability to recognize times when efficiency must be sacrificed for foreground performance, and can suspend and resume selected heavy background processes in real time to maximize both foreground performance and background efficiency. CPU based video encoders and cryptocurrency miners are examples of programs which can benefit greatly from this feature, allowing you to leave them running while working on other things or even gaming, all while keeping your CPU cool and on demand foreground performance high. You might want to use this with virtual machines, but be advised that some virtualizers may intercept input with hooks, which can cause severe input lag when suspended, though you may be able to disable the input hooks in the respective settings of your virtualizer.

  This is the power state threshold that efficiency locker strict processes will be allowed to run.

  This setting is from your power scheme. Unless overridden, the tool will obey this setting. If this is not set to 0, some Chill Boost features might be inneffective because the tool may not be able to lower the value enough to make a difference.

  This setting is from your power scheme. Unless overridden, the tool will obey this setting. If this is not set to 100, some Chill Boost features might be inneffective because the most impactful processor state change is usually the jump between 99 and 100. A jump between 90 and 99 might do absolutely nothing, for example.

  Overriding the minimum power state can increase the range at which Chill Boost is allowed to operate. This lets you use all of the settings of a more restricted power scheme, but still run the processor down to this level based on your other Chill Boost settings. This can prevent confusion with Chill Boost appearing to not work when it is actually just obeying your existing power plan settings.

  Overriding the maximum power state can increase the range at which Chill Boost is allowed to operate. This lets you use all of the settings of a more restricted power scheme, but still run the processor up to this level based on your other Chill Boost settings. This can prevent confusion with Chill Boost appearing to not work when it is actually just obeying your existing power plan settings.

  When using the chill boost auto calibration feature, efficiency estimations are used to select optimum power levels for various features. The power estimation formula looks like this:
Efficiency = Clock ^ ClockEstimationExponent / Voltage ^ VoltageEstimationExponent
I first thought that the value 2 would work fine, because increasing the voltage with the same resistance will also increase the current proportionally. However, processors are more complicated than that, so I played with it and selected a default value that gave me better results.

  When using the chill boost auto calibration feature, efficiency estimations are used to select optimum power levels for various features. The power estimation formula looks like this:
Efficiency = Clock ^ ClockEstimationExponent / Voltage ^ VoltageEstimationExponent
I first thought that the value 1 would work fine, because getting more work done with the same amount of power would increase efficiency proportionally. However, processors are more complicated than that, so I played with it and selected a default value that gave me better results.

  When using the chill boost auto calibration feature, power points are checked in a binary search pattern. Different power points get tested different amounts of time, and all of the data is used to provide a better estimation. Some power points may only be tested once or a small number of times in this fashion. This setting will make sure that each power point is tested at least this number of times.

  This is the maximum number of samples per second that the auto calibration feature will take. If this value is too high, the tool may pick up mismatched samples. If the value is too low, auto calibration may take a long time.

  If enabled, SMT (also known has hyper-threading on Intel) will be used during calibration. This can improve the accuracy of the efficiency data by taking into account this capability. Including SMT also allows higher core power usage during testing which can improve precision, as smaller power usage values are more difficult to measure.

  Using this option, you can run the auto calibration with as many cores as you like. Calibration is more stressful on your hardware with more cores, and testing too many cores may adversely affect system and tool performance. Testing additional cores can improve the quality of the measurements taken during calibration.

  Runs Chill Boost features in a separate priority process to ensure that it can work even if other priority processes on your computer are hogging all of the resources.

  Select the desired priority for the Chill Boost process.

  This is the number of hours Chill Boost has been enabled. For performance and hardware longevity, updates at around a 6 minute interval.

  The estimated watt hours saved works by comparing the average energy efficiency when Chill Boost is limiting the power state to the average energy efficiency when Chill Boost is not limiting the power state. As a result, you may see weird behavior such as the value rising when the power state is not limited, and this is because the average efficiency changes as new data arrives. The other thing to consider about the watt hours saved, is that in most cases, the majority of the energy your computer is consuming is not in CPU cores, but in things like your GPU, monitors, RAM, and processor IO, and Chill Boost only helps optimise your CPU core energy consumption, so what might be an apparant 50% savings shown by this value will have a lesser impact on battery life, for example. That being said, if you use Chill Boost long enough, the savings does add up, and depending on how you use your computer, the savings may actually pay for your product license.

  Enables Chill Boost feature, which reduces the CPU power state in specific circumstances to improve performance.

  This value is the number of times per second the chill boost updates. Higher values will increase responsiveness of the feature, but also can increase load on the CPU.

  This value is the number of times per second the chill boost settings panel updates. Because the settings panel does not run on the same timer as the feature itself, displayed values may not exactly match up with what is actually happening. Usually you would want the display panel updating slower, as it uses more resources and throws off its own results when running too quickly.

  The reservoir size is how many seconds your CPU is allowed to run at full load before Chill Boost kicks in, and should be matched to your CPU cooling system. For example, if you have a water cooled system that can't keep up with your overclock and it takes 30 seconds for your computer to crash at full load, you might want to set this at 10 seconds to limit unnecessary throttling but still prevent the system from reaching conditions in which it would crash. If you have an air-cooled system or a tight overclock, temperature issues can hit much faster so you might be better off leaving this value at 0. The reservoir only applies when looking at load. Temperature limit settings will ignore reservoir settings.

  The reservoir fill rate is a multiplier on how many seconds are filled per second of CPU underutilization. If you are overclocking your CPU in a configuration that is not thermally stable at 100% load, you might outpace your heat dissipation and crash if you set this value too high. If you are not overclocking, your CPU should be expected to handle 100% load just fine, in which case this feature would be more about improving heat, noise, and energy management at lower values.

  This is the CPU usage percentage at which the stressed power state limit is triggered. This is extra useful when temperature sensors are unavailable or when temperature sensors do not respond fast enough. This threshold works in conjunction with the boost reservoir.

  This is the temperature at which the stressed power state limit is triggered. This target ignores the boost reservoir and tries to reduce the CPU temperature until it is below the target. CPUs already have similar mechanisms built in. However, when overclocking these mechanisms tend to be disabled, save for some last-ditch temperature controls which tend to limit only clock speed and not voltage. Even when not overclocking, these features are typically nonconfigurable, so this setting gives you more flexibility to efficiently keep temperatures low and noise down without sacrificing performance under light loads.

  This should be higher than the Chill Boost Temperature Target. It works similarly, but can make more drastic voltage reductions by dropping to an even lower power state. If you are overclocking, this would be your last line of defense outside of built-in emergency thermal limiters which may wait to kick in until as much as 100C. While the default is 75C, I am not saying that 75C is safe, but it surely is a lot safer than a 100C hardware limiter. Depending on your hardware, if you are reaching 75C without overclocking, this may be evidence that your cooling system is inadequate, installed improperly, or failing.

  This setting reduces your temperature allowances based on load. When this setting is 5 and the load is 100%, the temperature target and critical limit will be reduced by 5. At 0% load, the reduction would be 0. This allows the tool to respond faster than by simply going by the temperature sensors alone. This setting can allow the CPU to bounce back to high performance quicker when load is reduced. The setting also enables the tool to catch temperature spikes quicker.

  Temperature sensors can be glitchy sometimes. This is a very basic protection mechanism which ignores negative temperature values coming from the temperature sensor. On my system, I was getting odd temperature spikes during load tests because the sensor was sending back negative numbers from time to time, causing my temperature protections to not work correctly.

  This setting is a power state limit for dealing with load or temperature under stressed conditions. Depending on your hardware, the optimum value for this setting may vary wildly. The auto-calibration feature will select the power state with the second highest voltage, which usually offers both high efficiency and decent performance, but you could use the information from the auto-calibration table to optimize this value yourself. Lower values should reach more conservative power states, but the power states follow a step function that varies by hardware, so you have to lower the value enough to reach the next step before any actual change happens.

  This setting is a power state limit for dealing with load or temperature under critical conditions. The value 0 will enable the maximum voltage drop available. Higher values may still be effective without reducing performance as much. Processors have their own built-in protection mechanisms, but this setting can offer another layer of protection, which can come in especially handy when overclocking as some hardware protection mechanisms may be disabled. Auto-calibration will always set this value to 0 for maximum safety, but depending on your hardware you may be able to select a higher value which is stable under constant maximum load, in which case I would recommend setting this to the most efficient power state shown in the auto-calibration table.

  The Chill Boost Safety Mechanism exists in case you are using Chill Boost to thermally stabilize an overclock, so that your system does not go full throttle and crash before Chill Boost is able to run. Chill Boost only functions correctly while the tool is running. This mechanism attempts to leave your computer in the reduced power state if the computer crashes until the tool is running again. This feature could potentially cause Chill Boost to limit power more often than intended. Also, with this setting enabled, your power plan will not be reverted back to your normal power plan when you exit Simplode Suite normally, so you might have poor performance when the tool is not running and not remember why. Many computers reset their power plan on restart for whatever reason, and this safety mechanism will not work correctly in this case, though you could lower the maximum CPU power state in the power plan to which your system reverts so that you can still have the same sort of protection.

  Chill Boost Efficiency Locker blocks background and low priority apps from switching your processor into performance mode. When a processor is in performance mode, efficiency losses can be enormous, leading to more heat, more noise, and possibly shorter device lifespans. We like performance, though, for things we are focused on, but often times a background process will put your device into performance mode unnecessarily. The heat can even reduce the performance of your foreground app, so this feature can even increase perceived performance.

  When the efficiency locker is enabled, this threshold determines when it is active. Other efficiency locker settings change specific aspects of this behavior, but in general the computer will be allowed to run at full throttle when the application you are currently focused on has at least one thread that is trying to use the CPU more than this threshold. Getting close to 100% thread load can be quite difficult because time spent waiting for resources does not count. With that in mind, you may need to keep this number unituitively low considering a thread at 60% load can still be starved for more processor power.

  Performance Optimized: In this mode, the feature will not engage until it has detected unnecessary boosting caused by background apps. Apps that you want to boost will be able to boost without delay.
Efficiency Optimized: In this mode, the feature will block boosting until it detects that an app that you want to boost needs boosting. This mode may delay boosting slightly.

  When enabled alongside the Chill Boost Efficiency Locker, it can more accurately detect when multithreaded apps have headroom for efficiency improvement. Sometimes multithreaded applications have exotic thread configurations which make it difficult to determine if they are facing a thread speed bottleneck. For applications where the total load is less than the thread load threshold, we can easily determine that we have room to increase efficiency. However, when total load is higher than the thread load threshold, threads could be cascading information to each other making them behave as a single thread with similar efficiency penalties, and if we judged simply be looking at the threads individually, we would incorrectly enter efficiency mode, noticeably reducing the performance of the app. By analyzing process CPU usage at small enough intervals, the tool is able to see moments when an app is completely caught up. The duration and cadence of these moments can be used to determine how much room we have for efficiency improvements without reducing performance even when threads are interacting in unknown ways.

  This is the threshold at which the Efficiency Locker Multithread Enhancement will consider the focused app busy enough to need maximum performance. To reduce the chance that a busy application may be throttled, the focus app will be considered busy from when it is triggered until the value falls below 0.5 if this threshold is above 0.5.

  When the Chill Boost Efficiency Locker activates, the max power state will be limited to this value. The default value of 99 is usually a substantial improvement in efficiency on its own, though the most efficient power state is likely lower than 99. The Auto Calibration feature can set this value to most efficient power state available. The efficiency locker may reduce the power state even lower than this setting depending on the other efficiency locker settings.

  The efficiency locker can sometimes cause unnecessary frame drops if it detects a brief period of favorable conditions. Higher values in this setting will increase the amount of time that the efficiency locker will wait before kicking in, reducing the chances that it will kick in at a bad time and cause a frame drop.

  These processes will only be allowed to run while the efficiency locker is active and not above the strict process energy state threshold. Use the file names of each process, separated by commas or new lines. While processes in the list are in the background and the maximum power state is above this value, they will be completely unresponsive. While processes in the list are in the foreground, the maximum power state will be limited to the threshold. This allows you to run selected processes at maximum efficiency while minimizing any negative impact on other foreground processes. There is no way to configure processes to run at different voltages simultaneously, so the only way to ensure efficiency for heavy background processes is to allow them to run only while the voltage is limited. Chill Boost Efficiency Locker offers the unique capability to recognize times when efficiency must be sacrificed for foreground performance, and can suspend and resume selected heavy background processes in real time to maximize both foreground performance and background efficiency. CPU based video encoders and cryptocurrency miners are examples of programs which can benefit greatly from this feature, allowing you to leave them running while working on other things or even gaming, all while keeping your CPU cool and on demand foreground performance high. You might want to use this with virtual machines, but be advised that some virtualizers may intercept input with hooks, which can cause severe input lag when suspended, though you may be able to disable the input hooks in the respective settings of your virtualizer.

  This is the power state threshold that efficiency locker strict processes will be allowed to run.

  This setting is from your power scheme. Unless overridden, the tool will obey this setting. If this is not set to 0, some Chill Boost features might be inneffective because the tool may not be able to lower the value enough to make a difference.

  This setting is from your power scheme. Unless overridden, the tool will obey this setting. If this is not set to 100, some Chill Boost features might be inneffective because the most impactful processor state change is usually the jump between 99 and 100. A jump between 90 and 99 might do absolutely nothing, for example.

  Overriding the minimum power state can increase the range at which Chill Boost is allowed to operate. This lets you use all of the settings of a more restricted power scheme, but still run the processor down to this level based on your other Chill Boost settings. This can prevent confusion with Chill Boost appearing to not work when it is actually just obeying your existing power plan settings.

  Overriding the maximum power state can increase the range at which Chill Boost is allowed to operate. This lets you use all of the settings of a more restricted power scheme, but still run the processor up to this level based on your other Chill Boost settings. This can prevent confusion with Chill Boost appearing to not work when it is actually just obeying your existing power plan settings.

  When using the chill boost auto calibration feature, efficiency estimations are used to select optimum power levels for various features. The power estimation formula looks like this:
Efficiency = Clock ^ ClockEstimationExponent / Voltage ^ VoltageEstimationExponent
I first thought that the value 2 would work fine, because increasing the voltage with the same resistance will also increase the current proportionally. However, processors are more complicated than that, so I played with it and selected a default value that gave me better results.

  When using the chill boost auto calibration feature, efficiency estimations are used to select optimum power levels for various features. The power estimation formula looks like this:
Efficiency = Clock ^ ClockEstimationExponent / Voltage ^ VoltageEstimationExponent
I first thought that the value 1 would work fine, because getting more work done with the same amount of power would increase efficiency proportionally. However, processors are more complicated than that, so I played with it and selected a default value that gave me better results.

  When using the chill boost auto calibration feature, power points are checked in a binary search pattern. Different power points get tested different amounts of time, and all of the data is used to provide a better estimation. Some power points may only be tested once or a small number of times in this fashion. This setting will make sure that each power point is tested at least this number of times.

  This is the maximum number of samples per second that the auto calibration feature will take. If this value is too high, the tool may pick up mismatched samples. If the value is too low, auto calibration may take a long time.

  If enabled, SMT (also known has hyper-threading on Intel) will be used during calibration. This can improve the accuracy of the efficiency data by taking into account this capability. Including SMT also allows higher core power usage during testing which can improve precision, as smaller power usage values are more difficult to measure.

  Using this option, you can run the auto calibration with as many cores as you like. Calibration is more stressful on your hardware with more cores, and testing too many cores may adversely affect system and tool performance. Testing additional cores can improve the quality of the measurements taken during calibration.

  Runs Chill Boost features in a separate priority process to ensure that it can work even if other priority processes on your computer are hogging all of the resources.

  Select the desired priority for the Chill Boost process.

  This is the number of hours Chill Boost has been enabled. For performance and hardware longevity, updates at around a 6 minute interval.

  The estimated watt hours saved works by comparing the average energy efficiency when Chill Boost is limiting the power state to the average energy efficiency when Chill Boost is not limiting the power state. As a result, you may see weird behavior such as the value rising when the power state is not limited, and this is because the average efficiency changes as new data arrives. The other thing to consider about the watt hours saved, is that in most cases, the majority of the energy your computer is consuming is not in CPU cores, but in things like your GPU, monitors, RAM, and processor IO, and Chill Boost only helps optimise your CPU core energy consumption, so what might be an apparant 50% savings shown by this value will have a lesser impact on battery life, for example. That being said, if you use Chill Boost long enough, the savings does add up, and depending on how you use your computer, the savings may actually pay for your product license.