element-hq / element-hq/element-call
Screensharing uses huge amounts of CPU
Open
A-Performance
A-Screen-Sharing
T-Defect
- Dominant language
- TypeScript
- Stars
- 996
- Forks
- 213
- Avg merge
- 1d 8h
- Merged PRs (30d)
- 55
Description
### Steps to reproduce
Often when I start a screenshare, it will max out every core on machine. Reports of similar from others too. We should investigate if there's something wrong here, or if this is just actually how much CPU it takes to encode a screenshare to full mesh participants. Does the amount of CPU scale with number of participants in the call?
### Outcome
#### What did you expect?
#### What happened instead?
### Operating system
_No response_
### Browser information
_No response_
### URL for webapp
_No response_
### Will you send logs?
Yes
Contributor guide
Assessment
This issue has not been assessed yet.