Good ballpark figures for front end and back end bound

Chris_A_ — Thu, 15 Jan 2015 08:54:28 GMT

Could someone please shed some light on what good ball park figures are for the front and back end bound metrics obtained via VTune, below are the formulae I've managed to obtain for the CPU KPI, if I have interpretted these correctly, Back end bound should be as close to zero as possible as should front end bound, however, what are practical values for these figures - good rough ball parks, also is my interpretation of these correct.

Front end bound ( smaller is better ? ) = IDQ_NOT_DELIVERED.CORE / (4 * Clock ticks)

Bad speculation = (UOPS_ISSUED.ANY – UOPS.RETIRED.RETIRED_SLOTS + 4 * INT_MISC.RECOVERY_CYCLES) / (4 * Clock ticks)

Retiring = UOPS_RETIRE_SLOTS / (4 * Clock ticks)

Back end bound ( ideally, should = 1 - Retiring) = 1 – (Front end bound + Bad speculation + Retiring)

topic Good ballpark figures for front end and back end bound in Software Tuning, Performance Optimization & Platform Monitoring

Good ballpark figures for front end and back end bound