Ezserver

C/C++ Memory-Based Streaming Engine

Architecture Comparison
  • ◉ Ezserver (Memory-Based Streaming): Streams video directly from memory, ensuring faster data transfer and reduced reliance on disk operations.
  • ◉ XUI, Xtream UI and FFMpeg-based Panels. (Disk-Based Streaming): Relies on saving video files to disk and serving them via a web server, which introduces latency and potential disk bottlenecks.

Comparative Analysis

Aspect

Ezserver

(Memory-Based Streaming)

XUI, Xtream UI, etc.

(Disk-Based Streaming)

Video Storage

Uploads video links and temporarily stores them in memory with a buffer size.

Uploads video links and uses ffmpeg to save video data to disk in file format.

Streaming Mechanism

Streams videos directly from memory to connected players.

Streams videos by having players access saved files via nginx.

Streaming Speed

Faster due to memory-based streaming.

Slower, as it requires disk read operations.

Mass Connections

Efficiently handles mass connections as streaming is memory-based.

Disk access may become a bottleneck, causing blocked issues under heavy load.

Disk Usage

Minimal disk usage, reducing risks of disk crashes.

High disk usage, increasing the risk of disk failure.


Benchmark

Channel Buffer Time

Service

Buffer Time (Seconds)

Performance

Ezserver

Faster

XUI One

Slower

Benchmark conditions:

Server Location: Brazil, Same Channel source: 3Mbps, VLC player Location: Taiwan

Video resolution: 1920x 1080, Frame rate: 25, Codec: H264 - MPEG-4 AVC

Audio Sample rate: 48000Hz, Bits per sample: 32, Codec: ADTS