Thank you for helping us improve the quality of Unity Documentation. Although we cannot accept all submissions, we do read each suggested change from our users and will make updates where applicable.
CloseFor some reason your suggested change could not be submitted. Please <a>try again</a> in a few minutes. And thank you for taking the time to help us improve the quality of Unity Documentation.
CloseSets the time-slice allocated per frame for asynchronous texture and mesh data uploads.
The minimum value is 1 millisecond and the maximum value is 33 milliseconds.
The asyncUploadTimeSlice property defines the maximum amount of time, in milliseconds, the CPU dedicates to asynchronously uploading texture or mesh data during each frame. Unity's asynchronous upload system uses this time-sliced approach to ensure that upload operations don't block the main thread and that performance remains smooth during runtime. If there are no pending asynchronous upload operations remaining, Unity reallocates this time to other CPU tasks, optimizing system performance.
This property is useful for prioritizing asynchronous asset uploads in scenes with frequent small texture or mesh loads while maintaining control over CPU usage. By increasing the time slice, Unity may be able to upload more assets on a given frame. Conversely, reducing this value ensures that asset uploads consume less CPU time per frame, leaving more resources available for other tasks, such as gameplay logic or physics calculations.
using UnityEngine;
public class StartupExampleScript : MonoBehaviour { void Start() { // Set time-slice to 2 ms QualitySettings.asyncUploadTimeSlice = 2; } }
The asynchronous upload pipeline allows Unity to perform time-sliced asynchronous texture and mesh data uploads on the render thread. This pipeline provides fine-grained control over memory usage and the time-slicing mechanism, ensuring that asset uploads don't block the main thread and are managed efficiently during runtime. To minimize memory allocations, the pipeline re-uses a ring buffer to process texture and mesh data. You can adjust the size of this ring buffer using the asyncUploadBufferSize property.
This functionality is useful for optimizing scenes with frequent dynamic asset loading or high-memory environments, such as open-world games or applications with large textures and meshes. By allowing asynchronous data uploads, Unity ensures smooth performance and avoids sudden spikes in memory usage or frame times during intensive loading operations.
The asynchronous upload pipeline minimizes allocations, except for the unavoidable allocations performed by the graphics driver itself. It's designed to reuse existing memory efficiently, reducing fragmentation and overhead.
Additional resources: Loading texture and mesh data.
Did you find this page useful? Please give it a rating:
Thanks for rating this page!
What kind of problem would you like to report?
Thanks for letting us know! This page has been marked for review based on your feedback.
If you have time, you can provide more information to help us fix the problem faster.
Provide more information
You've told us this page needs code samples. If you'd like to help us further, you could provide a code sample, or tell us about what kind of code sample you'd like to see:
You've told us there are code samples on this page which don't work. If you know how to fix it, or have something better we could use instead, please let us know:
You've told us there is information missing from this page. Please tell us more about what's missing:
You've told us there is incorrect information on this page. If you know what we should change to make it correct, please tell us:
You've told us this page has unclear or confusing information. Please tell us more about what you found unclear or confusing, or let us know how we could make it clearer:
You've told us there is a spelling or grammar error on this page. Please tell us what's wrong:
You've told us this page has a problem. Please tell us more about what's wrong:
Thank you for helping to make the Unity documentation better!
Your feedback has been submitted as a ticket for our documentation team to review.
We are not able to reply to every ticket submitted.