golang/owncast
1
0
Fork 0
mirror of https://github.com/owncast/owncast.git synced 2025-11-02 20:23:29 +08:00
Code Issues Packages Projects Releases Wiki Activity
Files
owncast/doc/troubleshooting.md
Gabe Kangas 4c3da2704f Simple hardware metrics collection + alerting (#115) 
* Add CPU and RAM usage alerting

* Create basic troubleshooting document to point alerts at

* Limit max number of hardware values collected

* Save metric value with the point in time it was taken
2020-08-27 00:37:32 -07:00

1.1 KiB
Raw Blame History

CPU and RAM usage alerts

If your hardware is being maxed out then your video may not be processed and delivered fast enough to keep up with the real-time requirements of live video.

Here are some steps you can try taking to resolve this.

  1. You may have too many bitrates defined as separate video quality variants. Try removing one.
  2. Change to a faster encoder preset in your configuration. If you're currently using veryfast, try superfast, for example.
  3. Try reducing the quality of the video you're sending to Owncast from your broadcasting software.
  4. If you've gone down to a single bitrate, changed the encoder preset to the fastest, and experimented with different qualities in your broadcasting software, it's possible the server you're running Owncast is just not powerful enough for the task and you might need to try a different environment to run this on.