[GH-ISSUE #2838] How much frpc can we start with one frps server? is there any limit for frpc? [Feature Request] #2268

Closed
opened 2026-05-05 13:27:42 -06:00 by gitea-mirror · 2 comments
Owner

Originally created by @ranjeet-pivotchain on GitHub (Mar 13, 2022).
Original GitHub issue: https://github.com/fatedier/frp/issues/2838

Describe the feature request

How much frpc can we start with one frps server? is there any limit for frpc?
We have an unlimited subdomain so can we start unlimited frpc with one frps server?

Describe alternatives you've considered

No response

Affected area

  • Docs
  • Installation
  • Performance and Scalability
  • Security
  • User Experience
  • Test and Release
  • Developer Infrastructure
  • Client Plugin
  • Server Plugin
  • Extensions
  • Others
Originally created by @ranjeet-pivotchain on GitHub (Mar 13, 2022). Original GitHub issue: https://github.com/fatedier/frp/issues/2838 ### Describe the feature request How much frpc can we start with one frps server? is there any limit for frpc? We have an unlimited subdomain so can we start unlimited frpc with one frps server? ### Describe alternatives you've considered _No response_ ### Affected area - [ ] Docs - [ ] Installation - [ ] Performance and Scalability - [ ] Security - [ ] User Experience - [ ] Test and Release - [ ] Developer Infrastructure - [X] Client Plugin - [X] Server Plugin - [ ] Extensions - [ ] Others
gitea-mirror 2026-05-05 13:27:42 -06:00
Author
Owner

@blizard863 commented on GitHub (Mar 14, 2022):

It depends on many factors. Such as

  1. all frpc and frps on a single machine or not
  2. The cpu, mem of the machine where frps is located

The best way is download latest binary and benchmark it.

<!-- gh-comment-id:1066230575 --> @blizard863 commented on GitHub (Mar 14, 2022): It depends on many factors. Such as 1. all frpc and frps on a single machine or not 2. The cpu, mem of the machine where frps is located The best way is download latest binary and benchmark it.
Author
Owner

@github-actions[bot] commented on GitHub (Apr 14, 2022):

Issues go stale after 30d of inactivity. Stale issues rot after an additional 7d of inactivity and eventually close.

<!-- gh-comment-id:1098599469 --> @github-actions[bot] commented on GitHub (Apr 14, 2022): Issues go stale after 30d of inactivity. Stale issues rot after an additional 7d of inactivity and eventually close.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/frp#2268
No description provided.