GUI-Level Testing Scalability Scenarios

System Test Environment

Silk Performer 2019
Silk Test 21.0
4 GB RAM
BroadCom 57xx Gigabit Controller
Dual (2 x 2.4 GHz) processors
167 GB free space hard disk

Note: The results below should be used as a guideline only and your results will differ depending on the application under test and the available resources of specific Silk Performer agent machines.

Test Scenario

The following table lists the memory consumption of virtual users navigating through a web application such as the Insurance demo application using different GUI-level testing technologies of Silk Test. As the memory consumption per virtual user depends heavily on the AUT (browser, application), only the processes of the corresponding driver technology are listed.

		Private Memory
Silk Test Type	VUser(s)	PerfRun.exe	openAgent.exe	PerfSm.exe	Supplementary processes
Silk Test Classic	1	15,5 MB	861 MB	2 MB	partner.exe - 19 MB
Silk Test Classic	N	N x 15,5 MB	N x 861 MB	N x 2 MB	N x 19 MB
UFT Developer (Silk4J)	1	15,5 MB	861 MB	36,5 MB
UFT Developer (Silk4J)	N	N x 15,5 MB	N x 861 MB	N x 36,5 MB
UFT Developer (Silk4NET)	1	15,5 MB	680 MB	2,5 MB	vstest.console.exe - 25 MB testhost_x86.exe - 35 MB
UFT Developer (Silk4NET)	N	N x 15,5 MB	N x 680 MB	N x 2,5 MB	N x 60 MB

Additional Information

Additional information on executing the load test on machines which use Multiple Processors:

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.