- Unity Game Optimization
- Dr. Davide Aversa Chris Dickinson
- 294字
- 2021-06-24 12:12:58
The Memory area
The Memory area allows us to inspect the memory usage of the application in Breakdown View in the following two modes:
- Simple mode
- Detailed mode
Simple mode provides only a high-level overview of the memory consumption of subsystems. This include Unity's low-level Engine, the Mono framework (total heap size that is being watched by the garbage collector), graphical assets, audio assets and buffers, and even memory used to store data collected by the Profiler.
Detailed mode shows memory consumption of individual GameObjects and MonoBehaviours for both their native and managed representations. It also has a column explaining the reason why an object may be consuming memory and when it might be deallocated.
Note that information only appears in Detailed mode through manual sampling by clicking on the Take Sample <TargetName> button. This is the only way to gather information when using Detailed mode, since performing this kind of analysis automatically for each update would be prohibitively expensive:

Breakdown View also provides a button labelled Gather Object References, which can gather more in-depth memory information pertaining to some objects.
The Memory area will be a useful tool to use when we dive into the complexities of memory management, native versus managed memory, and the garbage collector in Chapter 8, Masterful Memory Management.
- WildFly:New Features
- Learning Apex Programming
- Computer Vision for the Web
- Java 開發從入門到精通(第2版)
- PHP程序設計(慕課版)
- Visual FoxPro 程序設計
- Implementing Cisco Networking Solutions
- App Inventor創意趣味編程進階
- Unity 3D腳本編程:使用C#語言開發跨平臺游戲
- SwiftUI極簡開發
- 交互式程序設計(第2版)
- Learning Android Application Testing
- 現代C:概念剖析和編程實踐
- 嵌入式Linux C語言程序設計基礎教程
- Learning Kotlin by building Android Applications