Recording

NeoLoad can record media content requests to provide simulation-specific statistics. The statistics help assess the media content display quality.

NeoLoad supports media requests issued through the HTTP and RTMP communication protocols.

HTTP protocol

In NeoLoad, a media request on the HTTP protocol is identified by the file extension or the response Content-Type. The parameters are defined in the Project Preferences panel under the Modules Manager category. For more information, see Media Streaming.

  1. Start a new record.
  2. Run the scenario you want to simulate subsequently.
  3. Terminate the record with the post-recording wizard.
RTMP protocol

In NeoLoad, a media request on the RTMP protocol is identified when the Flash client issues the play command. The command initiates the transfer of video/audio data by the server.

  1. Start a new record after activating the RTMP protocol.
  2. Run the scenario you want to simulate subsequently.
  3. Terminate the record with the post-recording wizard.
Post-recording wizard

To generate statistics about the media playback, the average downstream rate of the media must be defined in NeoLoad. NeoLoad can figure out the average rate of some codecs: MPEG-4, FLV, F4V, AVI, MP3, and IceCast. For more information, see Media contents.

When the average downstream rate cannot be processed in NeoLoad, it is necessary to specify it for each media request. The post-recording wizard lists all the media actions which have been recorded and whose downstream rate is unavailable.

A click on the icon Compute the average bitrate makes it possible to measure the average downstream rate. The media length in seconds and the overall size of the file must be specified.

Clicking OK displays the average downstream rate determined by NeoLoad.

  1. Select the action in the list.
  2. Edit the value of the Downstream column.
  3. When necessary, click Compute the average bitrate to use the Compute average bitrate wizard.