8.

The cockpit can ping all the clients to see which ones are currently available. The ping will last for 30 seconds, but can be stopped by clicking stand by. All available clients will respond by registering in the database. At the same time, the client records a number of values related to its environment. To see a list of available computers, click Computers Available on the cockpit. This is illustrated in Figure 9: Computers available overview. Along with the name of the computer, the session identification is presented, as well as a weight. The weight is used in multi-client environments to distribute the load of scripts according to the computer power. Therefore the default weight is set to the number of CPUs multiplied by the clock frequency.

@%20=58725AB5=.files/image009.jpg">

Figure 9: Computers available overview

Figure 10: Computer info collected displays the information collected when a client is pinged. This form can be accessed through Laboratory registration, Computers. Details of the computer’s memory, number of CPUs, clock frequency, processor name, operating system, and load weight are automatically collected. Information regarding the computer model and level 2 cache should be inputted. This information is collected for every client and object server participating in a benchmark run. An entry is also made for the database server. Unfortunately no information is currently collected. Learn more about this in the Laboratory concept section later in this lesson.

The list of computers available is used to decide how to dispense the benchmark users among clients.

@%20=58725AB5=.files/image010.jpg">

Figure 10: Computer info collected

Running the test

A number of parameters determine the execution of a Benchmark run. These can be found under Benchmark parameters. The most essential parameters are positioned to the right of the form.

@%20=58725AB5=.files/image011.jpg" align=left hspace=12 v:shapes="_x0000_s1027">Figure 11: Benchmark parameters

The default think time in the above form is obsolete in version 2.5.

The cockpit can ping all the clients to see which ones are currently available. The ping will last for 30 seconds, but can be stopped by clicking stand by. All available clients will respond by registering in the database. At the same time, the client records a number of values related to its environment. To see a list of available computers, click Computers Available on the cockpit. This is illustrated in Figure 9: Computers available overview. Along with the name of the computer, the session identification is presented, as well as a weight. The weight is used in multi-client environments to distribute the load of scripts according to the computer power. Therefore the default weight is set to the number of CPUs multiplied by the clock frequency.

@%20=58725AB5=.files/image009.jpg">

Figure 9: Computers available overview

Figure 10: Computer info collected displays the information collected when a client is pinged. This form can be accessed through Laboratory registration, Computers. Details of the computer’s memory, number of CPUs, clock frequency, processor name, operating system, and load weight are automatically collected. Information regarding the computer model and level 2 cache should be inputted. This information is collected for every client and object server participating in a benchmark run. An entry is also made for the database server. Unfortunately no information is currently collected. Learn more about this in the Laboratory concept section later in this lesson.

The list of computers available is used to decide how to dispense the benchmark users among clients.

@%20=58725AB5=.files/image010.jpg">

Figure 10: Computer info collected

Running the test

A number of parameters determine the execution of a Benchmark run. These can be found under Benchmark parameters. The most essential parameters are positioned to the right of the form.

@%20=58725AB5=.files/image011.jpg" align=left hspace=12 v:shapes="_x0000_s1027">Figure 11: Benchmark parameters

The default think time in the above form is obsolete in version 2.5.