Use the Results drop-down list to select which test results to view within the current project. This choice will be reflected in all subsequent result panels.

There are two ways to delete a test result:

Filtering by a specific virtual user displays only that virtual user's web pages and actions (containers, loops etc..).

Likewise, filtering by a specific population displays only that population's virtual users.

Likewise again, filtering by a specific load generator displays only that load generator's populations and virtual users. In this case, the statistics displayed are the ones pertaining to the selected load generator.

	Note
	The load generator filter is disabled by default. It can be enabled in the project preferences' "Runtime parameters" section. The change will take effect for the next test. See the section called “Statistics”.

An HTTP request is a physical request made to the server. NeoLoad measures statistics for these, such as response time, throughput etc..

A web page contains one or more HTTP requests.

A container contains one or more web pages and actions (containers, loops etc..).

Where web pages or containers are concerned:

A Push message is a specific type of message sent via the Push channel during a test. See the section called “Push Messages”.

Each time a Push message is executed, it results in a hit on that message. Several messages may be executed from a same server response via the Push channel.

The response time is taken as the time delay between the moment the server decides to update the client and the moment the client receives the update. In fact, when using a Push framework, the request response time (time between sending a request and receiving its response) is virtually meaningless.

NeoLoad calculates the response time using a timestamp embedded in the server response. Depending on the framework being used, the timestamp extraction needs to be configured manually. See the section called “Push Messages”.

	Important
	For the response times for Push message to be coherent, the load generators' and application server's system clocks need to be synchronized.

Where the server's timestamp cannot be extracted, or the calculated response time is negative (load injectors and server have not been synchronized), NeoLoad shows a response time of 0. If all the statistics for message response times show <0.01, make sure the machines are synchronized and check the regular expression used to extract the timestamp in the Push request's configuration.