7.

Each run has four flags that determine how the run is executed. The four flags are

Display dependent: using forms

Worker thread: Three-tier only. The benchmark user runs as a separate thread in the object server.

COM-spawned: The user runs in a COM object.

Batch processing: All batchable processes are sent to batch.

Some of flags exclude others. If the run is display-dependent, it cannot be running as a worker thread or COM-spawned. If the batch-processing flag is enabled, all processes that can be sent to batch are automatically sent. To execute these processes during a benchmark run, a special Benchmark Batch-client needs to be spawned.

Setting up the environment

The main setup components needed to start a benchmark run are the driver and a number of clients. See the setup in

Figure 6: A simple Benchmark setup. The driver controls the benchmark runs using the cockpit. The cockpit will be discussed later in this lesson.

@%20=58725AB5=.files/image006.jpg" align=left hspace=12 v:shapes="_x0000_s1026">Figure 6: A simple Benchmark setup

For an Axapta client to participate in a benchmark run, the client control must be opened. This can be opened from main menu, benchmark, client control.

Note:

Remember to open the client control in the benchmark company. See Figure 7: Benchmark client look.

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

Figure 7: Benchmark client look

The cockpit communicates with the client control through a simple record in the database. Therefore the client control polls the database every second, when it is in standby mode. Polling is the continuous checking of the database by the client control to see whether they are still connected or want to communicate.

When a benchmark run is started, it reduces the poll to every 30 seconds.

The Cockpit

The cockpit is where the benchmark is started and finished. All communication to the clients is handled using the cockpit. See Figure 8: Benchmark cockpit.

The cockpit consists of three sections:

One section relates to the current status, as well as a number of general commands and the form’s short cuts.

The second section relates to an on going run.

The third section of the cockpit relates to the set of runs that can be started.

Runs can be started individually or as a series. The buttons start clients and reset clients can be activated in the BMInternalUse feature key. The button Step distribution is only available with the extensions to the benchmark tool, available from TechNet.

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

Figure 8: Benchmark cockpit

Each run has four flags that determine how the run is executed. The four flags are

Display dependent: using forms

Worker thread: Three-tier only. The benchmark user runs as a separate thread in the object server.

COM-spawned: The user runs in a COM object.

Batch processing: All batchable processes are sent to batch.

Some of flags exclude others. If the run is display-dependent, it cannot be running as a worker thread or COM-spawned. If the batch-processing flag is enabled, all processes that can be sent to batch are automatically sent. To execute these processes during a benchmark run, a special Benchmark Batch-client needs to be spawned.

Setting up the environment

The main setup components needed to start a benchmark run are the driver and a number of clients. See the setup in

Figure 6: A simple Benchmark setup. The driver controls the benchmark runs using the cockpit. The cockpit will be discussed later in this lesson.

@%20=58725AB5=.files/image006.jpg" align=left hspace=12 v:shapes="_x0000_s1026">Figure 6: A simple Benchmark setup

For an Axapta client to participate in a benchmark run, the client control must be opened. This can be opened from main menu, benchmark, client control.

Note:

Remember to open the client control in the benchmark company. See Figure 7: Benchmark client look.

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

Figure 7: Benchmark client look

The cockpit communicates with the client control through a simple record in the database. Therefore the client control polls the database every second, when it is in standby mode. Polling is the continuous checking of the database by the client control to see whether they are still connected or want to communicate.

When a benchmark run is started, it reduces the poll to every 30 seconds.

The Cockpit

The cockpit is where the benchmark is started and finished. All communication to the clients is handled using the cockpit. See Figure 8: Benchmark cockpit.

The cockpit consists of three sections:

One section relates to the current status, as well as a number of general commands and the form’s short cuts.

The second section relates to an on going run.

The third section of the cockpit relates to the set of runs that can be started.

Runs can be started individually or as a series. The buttons start clients and reset clients can be activated in the BMInternalUse feature key. The button Step distribution is only available with the extensions to the benchmark tool, available from TechNet.

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

Figure 8: Benchmark cockpit