Search Issue Tracker
Won't Fix
Votes
0
Found in
2019.4
2020.3
2020.3.0f1
2021.1
2021.2
Issue ID
1327309
Regression
No
.NET HttpClient class is 2-3 times slower than TcpClient when uploading same File
Reproduction steps:
1. Open the lined "UploadSpeedTestProject"
2. Open Task Manager, sort by Network usage
3. Edit Line 19 of UploadTest.cs to match your device
4. In the UploadTest menuItem, click TestHttpClient, upload will start, check network usage
5. Click TestTcpClient, check network usage
Expected result: Upload time and network usage are the same (or very similar)
Actual result: HttpClient Upload is 2-3 times slower.
Reproducible with: 2019.4.26f1, 2020.3.7f1, 2021.1.6f1, 2021.2.0a16
Notes: The difference seems to be noticeable only during the first test, after that the speeds seem to equalize for a while
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Assets are created in the Package folders when creating assets via custom buttons in the Inspector window or other windows
- “Select” windows are named differently on Windows and macOS
- [Windows] No minimum “Select” window size
- Enabling “Editor Extension Authoring” in UI Builder doesn’t dirty the document and saving with shortcut doesn’t persist the state
- WebRequest.Create() function fails with "URI prefix is not recognized" errors when the project is built for Linux Standalone or Windows Dedicated Server
Resolution Note (2022.1.X):
The overhead of the HttpClient accounts for this difference and can be observed with Mono, .Net Framework and .Net Core. However this test case does highlight a performance difference with the TLS provider un Unity vs. .Net Core and Mono. This is something that we have added to our backlog to investigate in a future release.