[object Object] Icon

Learn how to create, start, manage and modify Encodings

[object Object] Icon

Learn how to create, start, manage and modify Players

[object Object] Icon

Learn how to create, start, manage and modify Analyticss

Docs Home
User shortcuts for search
Focus by pressing f
Hide results by pressing Esc
Navigate via   keys

Thu Jul 16 2020

How we measure buffering in Bitmovin Analytics

Thu Jul 16 2020

Two types of buffering measurementsLink Icon

As buffering is one of the most important video metrics to track, we try to be as precise as possible in measuring buffering. Hence, in Bitmovin Analytics buffering is measured by two components.

  1. We start buffering measurements once the player sends out a “buffered” event.
  2. After an initial buffering time of 3 seconds, we deploy a heartbeat, checking every additional 5,10,30, and 59 seconds whether the user session is still active.

Example of the buffering heartbeat from row 10-13: Impression Log showing buffering heartbeat

After two minutes of sequential buffering a session is considered timed-out and a ANALYTICS_BUFFERING_TIMEOUT_REACHED error is thrown.

Buffering heartbeats have been deployed from the following collector versions onwards:

Give us feedback