{"id":15109,"date":"2024-04-12T09:59:45","date_gmt":"2024-04-12T09:59:45","guid":{"rendered":"https:\/\/ceeblue.net\/?p=15109"},"modified":"2024-04-12T14:18:23","modified_gmt":"2024-04-12T14:18:23","slug":"latency-benchmarks","status":"publish","type":"post","link":"https:\/\/ceeblue.net\/latency-benchmarks\/","title":{"rendered":"Real-World End-to-End Latency Benchmarks by Protocol"},"content":{"rendered":"\n
Prospective customers often ask us:<\/p>\n\n\n\n
The purpose of this article is to provide answers to these questions with as few asterisks as possible.<\/p>\n\n\n\n
The Ceeblue Media Fabric can provide latencies as low as sub-200 milliseconds, end-to-end. Of course, the latency of real-time workflows depends on the successful optimization of many different factors at different stages. Each of our customers\u2019 integrations is unique and represents different benefits and challenges, and none will obtain the exact results shown here. We are providing these anecdotal results so that our customers can get a sense of what they can expect when using the most bleeding-edge real-time solution available today.<\/p>\n\n\n\n
In January 2024, Ceeblue performed a series of real-world tests using different combinations of players, ingest protocols and delivery protocols.<\/p>\n\n\n\n
This testing is not exhaustive, and there are protocols and combinations of protocols that we happily support but which were excluded from this process so that we could focus on our most-requested formats.<\/p>\n\n\n\n
These realistic benchmarks will not only provide invaluable guidance for our customers, based on real-world results, but will also contribute to a comprehensive report being drafted by the CDN Alliance\u2019s Low Latency Workgroup<\/strong><\/a>, which Ceeblue co-chairs<\/strong><\/a>, regarding the state of low-latency solutions.<\/p>\n\n\n\n GStreamer was used to push the stream from the residence of one of our engineers, using a residential internet connection, with a standard, ISP-provided WiFi router.<\/p>\n\n\n\n The engineer then opened the webpage which loads our demo environment. This environment utilizes on-canvas embedded epoch timestamps which record the exact moment the video is streamed from the source browser.<\/p>\n\n\n\n When playback occurs on the viewer\u2019s browser, this timestamp is compared to the current time and the difference between these two times is displayed as the end-to-end latency of the stream. <\/p>\n\n\n\n Ceeblue provides incredibly fast start times, and in the first second or two a stream will have slightly higher latency (around 1 second for WebRTC, for example); but this latency quickly drops down to a stable latency that is much lower, which our engineer has duly recorded for each and every combination of ingest protocol, output protocol, and player on the table below.<\/p>\n\n\n\nThe Testing Environment: True End-to-End Latency<\/h2>\n\n\n\n
\n