Executing a 1 VUser test over a 10 minute period
|
Executing a 5 VUser increasing workload test over a 10 minute period, with VUser per process set to 1
|
Executing a 5 VUser increasing workload test over a 10 minute period, with VUser per process set to 5
|
Executing a 10 VUser increasing workload test over a 10 minute period, with VUser per process set to Automatic Calculation
(resulting in 10
PerfRun.exe files being launched)
|
Executing a 20 VUser increasing workload test over a 10 minute period, with VUser per process set to 20
|
Executing a 25 VUser increasing workload test over a 15 minute period, with VUser per process set to 25
|
Executing a 36 VUser increasing workload test over a 18 minute period, with VUser per process set to 18 (for example, two
PerfRun.exe files executing all 36 VUsers)
|
As long as you have more replay engines (PerfRun.exe) running than you have CPUs available on the machine, the current implementation of GUI-level support in Silk Performer does not have any limitations regarding the number of processors that can be used on a Silk Performer agent installation. During a load test scenario, each Silk Performer replay engine (PerfRun.exe) will be bound to a particular processor in a round robin method, for example: PerfRun.exe1 to CPU1, PerfRun.exe2 to CPU2, PerfRun.exe3 to CPU3, perfRun.exe4 to CPU4, and so on.