rustdesk / rustdesk/rustdesk-server
Very low fps
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 10.4k
- Forks
- 2.6k
- PR merge metrics
- No merged PRs in 30d
Description
Describe the bug
I'm using a self hosted rustdesk-server on my Mac with docker.
But when connecting to my remote desktop I barely get 20 fps (max) and an average of 14 fps.
Why it is slow? Even is being hosted on my own private network (LAN), I also have the custom image settings at max in the client, but is still slow.
Describe the environment
- Install environment: docker
- If available, the
docker-compose.yamlfile:
version: '3'
networks:
rustdesk-net:
external: false
services:
hbbs:
container_name: hbbs
ports:
- 21115:21115
- 21116:21116
- 21116:21116/udp
- 21118:21118
image: rustdesk/rustdesk-server:latest
command: hbbs
volumes:
- ./hbbs:/root
# network_mode: "host"
networks:
- rustdesk-net
depends_on:
- hbbr
restart: unless-stopped
hbbr:
container_name: hbbr
ports:
- 21117:21117
- 21119:21119
image: rustdesk/rustdesk-server:latest
command: hbbr
volumes:
- ./hbbr:/root
# network_mode: "host"
networks:
- rustdesk-net
restart: unless-stopped
How to Reproduce the bug
Steps to reproduce the behavior:
- Given the previously described environment
- Do this and that
- I get this error
Expected behavior
I should get at least 40 fps > since is being ran LAN...
Additional context
Thanks!
Notes
- Please write in english only. If you provide some images in different languages, you're required to write a translation in english.
- In any case, NEVER put here the content if your
id_ed25519file
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the supplied docker-compose.yaml and verify the reported LAN setup, Docker image, published ports, and connection path. Reproduce the 14–20 FPS result while collecting the relevant client and server details; done should be a confirmed cause with a reproducible test or a documented explanation of the expected behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, rust
- Domain
- backend, networking, performance
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100