We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Describe the bug When streaming to SRS using RTMP and playing back with HTTP-FLV, the CPU utilization is very high, exceeding 25%.
Version 6.0.113
6.0.113
To Reproduce Steps to reproduce the behavior:
env SRS_LISTEN=1935 \ SRS_DAEMON=off \ SRS_VHOST_MIN_LATENCY=on \ SRS_VHOST_PLAY_MW_LATENCY=0 \ SRS_HTTP_SERVER_ENABLED=on \ SRS_VHOST_HTTP_REMUX_ENABLED=on \ SRS_VHOST_HTTP_REMUX_MOUNT=[vhost]/[app]/[stream].flv \ ./objs/srs -e
ffmpeg -re -i doc/source.flv -c copy -f flv rtmp://localhost/live/livestream
curl http://localhost:8080/live/livestream.flv -o /dev/null
Expected behavior Without transcoding, the CPU should less than 1%.
Screenshots
Additional context No such problem if publishing and playing by RTMP, or set SRS_VHOST_PLAY_MW_LATENCY=350
SRS_VHOST_PLAY_MW_LATENCY=350
TRANS_BY_GPT4
The text was updated successfully, but these errors were encountered:
Workaround: If not using WebRTC, set SRS_VHOST_PLAY_MW_LATENCY=100 or higher. Or simply keep the default value, not set this config item.
SRS_VHOST_PLAY_MW_LATENCY=100
Sorry, something went wrong.
winlinvip
No branches or pull requests
Describe the bug
When streaming to SRS using RTMP and playing back with HTTP-FLV, the CPU utilization is very high, exceeding 25%.
Version
6.0.113
To Reproduce
Steps to reproduce the behavior:
ffmpeg -re -i doc/source.flv -c copy -f flv rtmp://localhost/live/livestream
curl http://localhost:8080/live/livestream.flv -o /dev/null
Expected behavior
Without transcoding, the CPU should less than 1%.
Screenshots
Additional context
No such problem if publishing and playing by RTMP, or set
SRS_VHOST_PLAY_MW_LATENCY=350
TRANS_BY_GPT4
The text was updated successfully, but these errors were encountered: