- 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.
- Mastering Concurrency Programming with Java 8
- Spring Boot 2實戰之旅
- ServiceNow Application Development
- Google Apps Script for Beginners
- Learning Real-time Processing with Spark Streaming
- Python語言程序設計
- Python自動化運維快速入門
- 跟老齊學Python:輕松入門
- Java程序設計與計算思維
- INSTANT Django 1.5 Application Development Starter
- Node.js全程實例
- Instant Zurb Foundation 4
- jQuery技術內幕:深入解析jQuery架構設計與實現原理
- 交互式程序設計(第2版)
- Applied Deep Learning with Python