VideoStreamingJob
One streaming session of a given resolution and duration consumed against a VideoStreaming service. Bandwidth, CPU, and RAM are derived from the resolution, refresh rate, and the service-level cost coefficients.
Params
name
A human readable description of the object.
service
VideoStreaming service that hosts the stream.
An instance of VideoStreaming.
resolution
Display resolution as a label like "1080p (1920 x 1080)". The pixel count is parsed from the label and used to estimate the dynamic bitrate.
For example, 1080p (1920 x 1080).
video_duration
Duration of one streaming session, used as the request duration.
Unit: minute.
refresh_rate
Frames-per-second rate of the stream. Higher refresh rates increase the bitrate proportionally.
Unit: 1 / second.
data_stored
Net change in stored data per session. Usually 0 for streamed video.
Unit: megabyte_stored.
Backwards links
Calculated attributes
hourly_occurrences_per_usage_pattern
Hourly count of job invocations broken down by usage pattern, derived from when each usage pattern's journeys start and at what point in the journey this job is triggered.
Example value: {
UsagePattern usage pattern (e28419e5-c9b): 26298 values from 2025-01-01 00:00:00+00:00 to 2028-01-01 18:00:00+00:00: first=9 , last=4 , mean=5 , min=1 , max=9 , std=2.58 ,
}
Depends directly on:
- Hourly nb of pattern occurrences (UTC)
- Journeys per pattern occurrence
- Times per journey
- Times per step
through the following calculations:
You can also visit the link to Hourly occurrences in usage pattern’s full calculation graph.
hourly_avg_occurrences_per_usage_pattern
Hourly count of job invocations averaged with respect to job duration, so a job that runs longer than an hour contributes a fractional occurrence to several modeling buckets.
Example value: {
UsagePattern usage pattern (e28419e5-c9b): 26298 values from 2025-01-01 00:00:00+00:00 to 2028-01-01 18:00:00+00:00: first=3 , last=1.33 , mean=1.67 , min=0.333 , max=3 , std=0.861 ,
}
Depends directly on:
through the following calculations:
You can also visit the link to Average hourly occurrences in usage pattern’s full calculation graph.
hourly_data_transferred_per_usage_pattern
Hourly volume of data transferred over the network by this job, broken down by usage pattern.
Example value: {
UsagePattern usage pattern (e28419e5-c9b): 26298 values from 2025-01-01 00:00:00+00:00 to 2028-01-01 18:00:00+00:00: first=8.4 GB, last=3.73 GB, mean=4.67 GB, min=933 MB, max=8.4 GB, std=2.41 GB,
}
Depends directly on:
through the following calculations:
You can also visit the link to Hourly data transferred in usage pattern’s full calculation graph.
hourly_data_stored_per_usage_pattern
Hourly net change in storage volume caused by this job, broken down by usage pattern.
Example value: {
UsagePattern usage pattern (e28419e5-c9b): 26298 values from 2025-01-01 00:00:00+00:00 to 2028-01-01 18:00:00+00:00: first=0, last=0, mean=0, min=0, max=0, std=0,
}
Depends directly on:
through the following calculations:
You can also visit the link to Hourly data stored in usage pattern’s full calculation graph.
hourly_avg_occurrences_across_usage_patterns
Total hourly count of duration-averaged job invocations summed over every usage pattern.
Example value: 26298 values from 2025-01-01 00:00:00+00:00 to 2028-01-01 18:00:00+00:00: first=3 , last=1.33 , mean=1.67 , min=0.333 , max=3 , std=0.861
Depends directly on:
through the following calculations:
You can also visit the link to Hourly average occurrences across usage patterns’s full calculation graph.
hourly_data_transferred_across_usage_patterns
Total hourly volume of data transferred over the network by this job, summed over every usage pattern.
Example value: 26298 values from 2025-01-01 00:00:00+00:00 to 2028-01-01 18:00:00+00:00: first=8.4 GB, last=3.73 GB, mean=4.67 GB, min=933 MB, max=8.4 GB, std=2.41 GB
Depends directly on:
through the following calculations:
You can also visit the link to Hourly data transferred across usage patterns’s full calculation graph.
hourly_data_stored_across_usage_patterns
Total hourly net change in storage volume caused by this job, summed over every usage pattern.
Example value: 26298 values from 2025-01-01 00:00:00+00:00 to 2028-01-01 18:00:00+00:00: first=0, last=0, mean=0, min=0, max=0, std=0
Depends directly on:
through the following calculations:
You can also visit the link to Hourly data stored across usage patterns’s full calculation graph.
hourly_avg_occurrences_per_coordinate
Duration-averaged hourly occurrences for one web step or one recurrent server need within one usage pattern.
Example value: {
usage pattern / user journey / 20 min streaming: 26298 values from 2025-01-01 00:00:00+00:00 to 2028-01-01 18:00:00+00:00: first=3 , last=1.33 , mean=1.67 , min=0.333 , max=3 , std=0.861 ,
}
Depends directly on:
- Hourly nb of pattern occurrences (UTC)
- Journeys per pattern occurrence
- Times per journey
- Times per step
- Request duration
through the following calculations:
You can also visit the link to Average hourly occurrences of Video streaming job in 20 min streaming for usage pattern’s full calculation graph.
hourly_data_transferred_per_coordinate
Hourly network data transferred for one web-step or recurrent-server-need occurrence coordinate.
Example value: {
usage pattern / user journey / 20 min streaming: 26298 values from 2025-01-01 00:00:00+00:00 to 2028-01-01 18:00:00+00:00: first=8.4 GB, last=3.73 GB, mean=4.67 GB, min=933 MB, max=8.4 GB, std=2.41 GB,
}
Depends directly on:
- Average hourly occurrences of Video streaming job in 20 min streaming for usage pattern
- Data transferred
- Request duration
through the following calculations:
You can also visit the link to Hourly data transferred by Video streaming job in 20 min streaming for usage pattern’s full calculation graph.
request_duration
Request duration of one streaming session, equal to the chosen video duration.
Example value: 20 min
Depends directly on:
through the following calculations:
You can also visit the link to Request duration’s full calculation graph.
dynamic_bitrate
Estimated bitrate of the stream, equal to the pixel count parsed from the resolution times bits-per-pixel times refresh rate.
Example value: 0.778 MB/s
Depends directly on:
through the following calculations:
You can also visit the link to Dynamic bitrate’s full calculation graph.
data_transferred
Data transferred per session, equal to the dynamic bitrate times the video duration.
Example value: 933 MB
Depends directly on:
through the following calculations:
You can also visit the link to Data transferred’s full calculation graph.
compute_needed
CPU consumed per session, equal to the service's per-bitrate CPU cost times the dynamic bitrate.
Example value: 0.00311 cpu core
Depends directly on:
through the following calculations:
You can also visit the link to CPU needed’s full calculation graph.
ram_needed
RAM consumed per session, equal to the service's per-user RAM buffer.
Example value: 50 MB ram
Depends directly on:
through the following calculations:
You can also visit the link to RAM needed’s full calculation graph.