2022-06-23
4576
#unity
James LaFritz
120597
Jun 23, 2022 â‹… 16 min read

Performance in Unity: async, await, and Tasks vs. coroutines, C# Job System, and burst compiler

James LaFritz I have been using the Unity Game Engine since 2015 and programming in C# since 2006. I started off as a hobbyist and developed it into a career with GameDevHQ. You can find me at GameDevHQ, GitHub, or my blog.

Recent posts:

A Guide To Graceful Degradation In Web Development

A guide to graceful degradation in web development

Implement graceful degradation in frontend apps by handling failures, mitigating API timeouts, and ensuring a seamless UX with fallbacks.

Rosario De Chiara
Feb 11, 2025 â‹… 4 min read
Building High-Performance Websites Using Htmx And Go

Building high-performance websites using htmx and Go

Use htmx and Go to build high-performance websites, leveraging server-side rendering and minimal JavaScript for fast and efficient applications.

Abhinav Anshul
Feb 10, 2025 â‹… 11 min read
improving ux with scroll-select box

How to improve UX with a scroll-select box

The scroll-select box is a great tool for frontend developers to improve the user experience of their applications. Learn how to build a scrollable date picker that mimics the iOS style, but with the exemption of the <select> element.

Emmanuel Odioko
Feb 7, 2025 â‹… 10 min read
Deploying Next.js apps with Deno Deploy

Deploying Next.js apps with Deno Deploy

For those just getting started with deploying their first application, Deno Deploy’s simplicity might be exactly what you need; no complex configuration files to wrestle with or cloud concepts to master before getting your app live.

Emmanuel Odioko
Feb 6, 2025 â‹… 5 min read
View all posts

4 Replies to "Performance in Unity: <code>async</code>, <code>await</code>, and <code>Tasks</code> vs. coroutines, C# Job System, and burst compiler"

  1. “Next, we start the task t1.wait. Lastly, we wait for the task to complete with t1.wait.”
    Am I missing something here, or is the point that we start the task and wait for it to complete in a single statement?

  2. It should have been t1.run to start the task and t1.wait to wait for it to complete. You can do it in one line with await t1.Run or using the factory method. The point is to show different ways if starting and waiting for tasks to complete.

    Typically you want to start all of the tasks. So they are all running in parallel, then you wait for a specific task to complete before moving on to other things, it really depends on what you are trying to accomplish.

    You might want to run one task and wait for it to complete before starting other task if they depend on things from the first task.

  3. Typically it’s not tasks run on the caller’s thread it’s that they synchronize back to the caller’s thread. Are you saying Unity is forcing Tasks to run on the main thread or that because you’re not using ConfigureAwait they’re synchronized to the Unity’s main thread by default?

  4. The parameter passed to the method version is 50,000, but to the async and coroutine versions it is 5,000. Yeah, that’s going to impact the testing.

Leave a Reply