Search Issue Tracker
Won't Fix
Won't Fix in 6000.0.X
Votes
0
Found in
2021.3.36f1
2022.3.22f1
2023.2.17f1
6000.0.0b13
Issue ID
UUM-68130
Regression
No
HTTPS requests are marginally slow when using HttpClient
How to reproduce:
1. Setup the server
2. Open the “UnitySlowHttpClient” project
3. Open the “MainScene”
4. Enter Play Mode
5. Observe the Console
Expected result: The very first HTTPS request is around 500-600ms
Actual result: The very first HTTPS request is around 2400-2500ms
Reproduced with: 2021.3.36f1, 2022.3.22f1, 2023.2.17f1, 6000.0.0b13
Reproduced on: Windows 11
Not reproduced on: No other environment tested
Notes:
1. Instructions on how to setup the server are provided in the internal comments
2. Reproducible in the Player
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
- AI Assistant upgrade banner's `Open package Manager` link doesn't work
- Sub-asset UI does not refresh when undoing Renderer Feature add or remove actions in a URP Renderer asset
- Scene flickers with a green tint when using Screen Space Ambient Occlusion and Contact Shadows with raytracing
- Scripts with null Components on GameObjects are not removed when calling GameObjectUtility.RemoveMonoBehavioursWithMissingScript
- Color Curve Key values remain visible after changing Curve type
Resolution Note:
After an exhaustive investigative profiling process we have concluded that it is not reasonably feasible to address the performance issues in mono's HttpClient web stack. We've isolated the source of the problem to be unfortunately fundamental to the way the code was written and would require a complete refactor to address. Our recommendation is to use the better performing UnityWebRequest for now until we address this issue in a later release.
Resolution Note (6000.0.X):
After an exhaustive investigative profiling process we have concluded that it is not reasonably feasible to address the performance issues in mono's HttpClient web stack. We've isolated the source of the problem to be unfortunately fundamental to the way the code was written and would require a complete refactor to address. Our recommendation is to use the better performing UnityWebRequest for now until we address this issue in a later release.