It is possible that a SilkPerformer Custom Timer can have a value, which is double the expected value, if the MeasureStop() function is accidently scripted twice. This occurs as the 'Count' for the Custom Timer is done at the point where the Custom Timer is stopped. As the MeasureStop() occurs twice, the count for this will be 2 when it should actually be 1. This will also affect the '#Overall Response Time' total, for the custom timer, as the calculation used to get the average will be incorrect: This can be resolved by removing the additional MeasureStop() function from the script. 2679111
↧