Recorder endpoint timeout

wyvasi

Member
Good day!
Some of request for recorder startup times out after 5000 ms. /rest-api/recorder/startup
Should I increase the request timeout?
Why would it take so much to respond?
Also I often get video quality complaints, can I something about this?
CPU usage no more than 25-30%.
WCS version 1355.

Thanks!
 
Last edited:

Max

Administrator
Staff member
Good day.
Some of request for recorder startup times out after 5000 ms. /rest-api/recorder/startup
Should I increase the request timeout?
Why would it take so much to respond?
Seems like hard drive is very slow. Also this may happen if WCS runs in docker container, in this case an additional tuning is needed to provide a stable CPU resources to the container: How to use Docker with WebRTC in production
 

wyvasi

Member
Does is matter if I run only one container on one virtual machine?
I should just add "--cpuset-cpus=0-15" for 16 cores?
 

wyvasi

Member
What is the IOPS recommended and how many streams we can record on an instance without problems?
 

wyvasi

Member
Does taking snapshots (calling /rest-api/stream/snapshot ) frequently affect the start of recording? We had at most 6 ongoing recordings when /rest-api/recorder/startup would timeout.
 

Max

Administrator
Staff member
Snapshots are not linked with Recording directly. It can be either docker-specific issue (i.e. not enough iops) or general issue.
To exclude docker issue, you can just deploy on a non-docker environment with stable iops.
 
Top