Search Issue Tracker
Not Reproducible
Votes
0
Found in
2021.2
2022.1
Issue ID
1354321
Regression
No
[Mac] Dedicated Server build only decreases Memory usage, CPU time and Build size remain the same as Standalone
How to reproduce:
1. Open new Unity Project
2. In Build Settings window, switch to Windows, Mac, Linux build target
3. In Build Settings window, enable Development Build and Autoconnect Profile
4. Build and run, note down the Memory usage, CPU time and Build size
5. In Build Settings window, switch to Dedicated Server build target
6. Build and run, note down the Memory usage, CPU time and Build size
7. Compare the Standalone and Dedicated Server build performance
Expected result: Decreased Memory usage, CPU time and Build size in Dedicated Server
Actual result: Decreased Memory usage in Dedicated Server, same CPU time and Build size as in Standalone build
Reproducible with: 2021.2.0b5, 2022.1.0a4
Could not test with: 2019.4.29f1, 2020.3.15f1, 2021.1.16f1 (Dedicated Server functionality not implemented)
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note (2022.1.X):
All three properties are decreased when building a larger project