When you accept the Baseline Results within Silk Performer, the Baseline Session Time and the Goal Session Time should be similar within the 'Calculate the Virtual Users' screen. Each time you accept a new set of Baseline results, the subsequent 'Baseline Session Time' and 'Goal Session Time' should also be updated. However, a known issue exists that on some instances the 'Goal Session Time' will stay static from a previous baseline run. A workaround to the problem is to alter the 'Goal Session Time' within the 'Calculate the Virtual Users' screen, so that it is similar to the Baseline Session Time or meets the requires which you set. The 'Goal Session Time' is utilized by the formula within the 'Calculate the Virtual Users' screen to determine Sessions Per Peak Hour and Max VUsers. The Goal Session Time is not static and can be configured based on your requirements. For example, if you are returned a value of 1.20 s for the Baseline Session Time and you feel that 1.30s would be a suitable session time, the Goal Session Time can be configured to this requirement, using the Static and Dynamic Thinktime options within the 'Calculate the Virtual Users' dialogue. The static and dynamic thinktime options modify the thinktimes by adding a static or dynamic think factor to the scripted value to reach specific goal session times. For a fuller understanding of this please see How do I set up a test workload so that the arrival rate remains constant at x transactions per second
↧