mirror of
https://github.com/fatedier/frp.git
synced 2026-05-15 08:05:49 -06:00
[GH-ISSUE #5058] Significant performance difference: direct SFTP transfer is fast but FRP port forwarding is much slower #3976
Labels
No labels
In Progress
WIP
WaitingForInfo
bug
doc
duplicate
easy
enhancement
future
help wanted
invalid
lifecycle/stale
need-issue-template
need-usage-help
no plan
proposal
pull-request
question
todo
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/frp#3976
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @khdxs7 on GitHub (Nov 14, 2025).
Original GitHub issue: https://github.com/fatedier/frp/issues/5058
Bug Description
Title:
Significant performance difference: direct SFTP transfer is fast but FRP port forwarding is much slower
Describe the issue
Hello, I’ve been using FRP for many years and it has always been reliable.
Recently I discovered a significant performance issue when comparing direct transfer speed with FRP forwarding.
When I upload or download files to my cloud server using direct SFTP, the speed is very fast (full bandwidth).
However, when I expose my local service via FRP (TCP type) and access it from the same cloud server, the transfer speed becomes much slower, sometimes only a small fraction of the SFTP speed.
To double-check this, I also tested with a simple local Nginx static file server and observed the same slow performance when accessed via FRP.
So in both cases:
This is the first time I noticed such a large gap in many years of using FRP.
Versions tested
frpc Version
0.65.0
frps Version
0.65.0
System Architecture
linux/amd64
Configurations
Configurations used
frps.toml:frpc.tomlLogs
There is no error in logs. CPU usage is low during transfer.
Steps to reproduce
Affected area
Update:
I wrote a Python program myself to implement a function similar to frp and conducted tests. However, the test results were the same as before. What is certain is that the problem lies with frp. It may be a mechanism or logic issue. I am not sure if this issue occurs in all versions.
@github-actions[bot] commented on GitHub (Nov 30, 2025):
Issues go stale after 14d of inactivity. Stale issues rot after an additional 3d of inactivity and eventually close.
@kkroid commented on GitHub (Dec 25, 2025):
@khdxs7 did you find the solution?
@ImZhangAo commented on GitHub (Jan 23, 2026):
Hello, I also have the same problem. Have you found a solution?