nextcloud / nextcloud/nextcloud-talk-recording

Nextcloud talk recording causes very high CPU usage

Open
#91 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug
Dominant language
Python
Stars
34
Forks
16
Avg merge
5d 5h
Merged PRs (30d)
4

Description

[!TIP]

How to use GitHub
  • Please use the 👍 reaction to show that you are affected by the same issue.
  • Please don't comment if you have no relevant information to add. It's just extra noise for everyone subscribed to this issue.
  • Subscribe to receive notifications on status change and new comments.

Steps to reproduce

  1. Start a video call in Nextcloud Talk (even with a sigle participant)
  2. Start recording (with camera activated or sharing the desktop)
  3. Server CPU usage will jump to 100%
Expected behaviour

I am running a Nexcloud instance on a fairly powerfull machine (12 cores), at most 2-4 should be processing the recording, not all of them.

When not recording performace is OK for video calls.

Actual behaviour

All the cores in the server jump to 100% usage.

Talk app

Using with nextcloud AIO, nextcloud version 33.0.3 (Nextcloud Hub 26)

Talk app version: 23.04

Custom Signaling server configured: no

Custom TURN server configured: no

Custom STUN server configured: no

Browser

Microphone available: yes

Camera available: yes

Operating system: Ubuntu

Browser name: Brave Browser (Chrome)

Browser version: 1.89.143

Browser log

Server configuration

Operating system: Ubuntu

Web server: Apache

Database: PostgreSQL

PHP version: 8.1/8.2/8.3

Nextcloud Version: 33.0.3

List of activated apps:

If you have access to your command line run e.g.:
sudo -u www-data php occ app:list
from within your server installation folder

Nextcloud configuration:

If you have access to your command line run e.g.:
sudo -u www-data php occ config:list system
from within your Nextcloud installation folder
Server log (data/nextcloud.log)
Insert your server log here

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the issue with a single-participant Nextcloud Talk call and recording enabled, then inspect the server CPU usage and the available nextcloud.log output. The issue is resolved when recording no longer drives every server core to 100% under the described setup.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
backend, performance
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.