immense / immense/Remotely

Hight CPU for dotnet remotely server dll

Open
#960 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
C#
Stars
5.1k
Forks
1.6k
PR merge metrics
No merged PRs in 30d

Description

Team, I'm facing this issue affecting several the virtual where Remotely is running. It is causing really slow performance to all Docker apps, including the Remotely server itself.
My deployment is under Linux docker 6.1.0-25-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.106-3 (2024-08-26) x86_64 GNU/Linux
It is a virtual machine under VMware. The VM has 20 cores and 35 GB RAM dedicated to that docker. I'm running other dockers instances but nothing that requires large resources. The docker is behind a nginx proxy manager. As a note Remotely is handling like 400 clients but when clients starts to increase over 150 the CPU issue appears. The funny things is the CPU availability on the docker server.
The Temporary solution was add a docker compose stop - down - up every day but I'm losing all client available connected to the remotely but that's is another issue.
Thanks in advance,
Attached a screenshot.

![Image](https://github.com/user-attachments/assets/6787226e-b321-418a-b3d7-fb8d563888b1)

Contributor guide

No contributing guide indexed for this repository

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

The report names no source file, test, or entry point. Start by reproducing the CPU increase under the reported Docker deployment when more than 150 clients are connected, then profile the Remotely server process and compare it with the daily restart behavior. Done means the cause is identified and the issue includes a verified fix or a documented reproduction boundary.

Written by the indexing model from the issue text.

Assessment

Tech stack
csharp, docker, linux, nginx
Domain
backend, devops, performance
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.