You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently FIRESTARTER needs to be optimized for the highest power consumption with an algorithm that will take a couple hours. This optimization will create highest power consumption on a specific SKU of a CPU generation. This ticket shows a way to optimize FS in two steps that should allow SKU variations and create very high (not highest) power consumption.
Optimize FS on a specific SKU with a lower number of cores. This will allow us to have a bigger power budget per core making it more ideal for those SKUs. For SKUs with a lower budget per core FS will push the CPU into power limit anyway.
This optimization should be done with only cache and register accesses. Prefetches to RAM should be added to causes a level of power consumption from the memory controllers.
The second part of the optimization will be done on any SKU. The results of the previous steps will be taken and RAM instruction incrementally added. Once peak power consumption is reached, the optimization is finished.
DoD
Implement a way to use a specific number of thread equally spaced out in the CPU. (i.e. a specific number of cores per CCX on Zen or physically spaced out on the 2D grid on Intel CPUs)
Allow optimization of caches and registers with a specific number of RAM prefetches
Implement 'fast-optimization' that adjusts the number of RAM accesses.
Evaluate the effectiveness of this optimization on different SKUs vs. optimizing for each SKU.
The text was updated successfully, but these errors were encountered:
Currently FIRESTARTER needs to be optimized for the highest power consumption with an algorithm that will take a couple hours. This optimization will create highest power consumption on a specific SKU of a CPU generation. This ticket shows a way to optimize FS in two steps that should allow SKU variations and create very high (not highest) power consumption.
DoD
The text was updated successfully, but these errors were encountered: