Thread Local Storage stack allocator example
Inspect the usage reports of the TLS stack allocator allocator.
Read time 2 minutesLast updated 10 days ago
This example uses the memory usage reports that Unity writes to the log when you close the Player or Unity Editor. To create this report, use the command line argument. To find your project's log files, follow the instructions on the log files page.
-log-memory-performance-statsTLS stack allocator usage reports
If a thread’s stack allocator is full, allocations fall back to the threadsafe linear allocator. A few overflow allocations are fine: 1 to 10 in a frame, or a few hundred during load. However, if the numbers grow every frame, you can increase the block sizes.
Main Thread Block Size custom value in the Fast Per Thread Temporary Allocators
To increase the block size, set the value in the Editor, or use the command line arguments. For more information, refer to Customizing native memory allocators.
The information in the usage report can help you select a block size that's appropriate for your application. For example, in the following main thread usage report, the load peaks at 2.7 MB, but the remaining frames are under 64 KB. You can reduce the block size from 4 MB to 64 KB and allow the loading frame to spill over the allocations:
[ALLOC_TEMP_TLS] TLS Allocator StackAllocators : [ALLOC_TEMP_MAIN] Peak usage frame count: [16.0 KB-32.0 KB]: 802 frames, [32.0 KB-64.0 KB]: 424 frames, [2.0 MB-4.0 MB]: 1 frames Initial Block Size 4.0 MB Current Block Size 4.0 MB Peak Allocated Bytes 2.7 MB Overflow Count 0 [ALLOC_TEMP_Job.Worker 18]
In the following example, the worker thread isn't used for large temporary allocations. To save memory, you can reduce the worker’s block size to 32 KB. This is useful on a multi-core machine, where each worker thread has its own stack:
[ALLOC_TEMP_Job.Worker 14] Initial Block Size 256.0 KB Current Block Size 256.0 KB Peak Allocated Bytes 18.6 KB Overflow Count 0