-
Notifications
You must be signed in to change notification settings - Fork 12
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
fixed bad naming, added requirement for jitter
- Loading branch information
1 parent
7c5d776
commit 76e5074
Showing
3 changed files
with
28 additions
and
2 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
File renamed without changes.
26 changes: 26 additions & 0 deletions
26
requirements/J/_posts/2023-12-05-minimize-jitter-in-data-streaming.md
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,26 @@ | ||
--- | ||
title: "Minimize jitter in real-time data streaming" | ||
tags: reliable operable | ||
related: jitter, predictability, latency | ||
permalink: /requirements/minimize-jitter | ||
--- | ||
|
||
<div class="quality-requirement" markdown="1"> | ||
|
||
### Overall goal: Reduce and control [jitter](/qualities/jitter) in the real-time streaming of data. | ||
|
||
|
||
**Stimulus**: Continuous transmission of real-time data (from sensors) over a network,. | ||
|
||
**Environment**: Operational phase under standard network conditions. | ||
|
||
**Response**: The system handles variations in delay of data packet delivery. | ||
|
||
**Response Measure**: | ||
|
||
* The variance in delay between data packets (jitter) should not exceed 5 milliseconds for 95% of the transmitted packets | ||
* In instances where jitter exceeds this threshold, the system should employ buffering mechanisms to smooth the data flow, ensuring that the effective jitter experienced by the end-user remains below 7 milliseconds | ||
* The system must detect and log instances of high jitter (above 5 milliseconds) in real-time, triggering alerts for the technical team when such instances exceed 5% of the total packets in any 10-minute window | ||
* During peak load times, the allowable jitter can increase to a maximum of 10 milliseconds, but such instances should not exceed 2% of the total packets transmitted in a 24-hour period. | ||
|
||
</div><br> |