To make burst even better I think burst needs to continue to improve it to make it able to burst compile incrementally instead of repeatedly burst compile same piece of code. Currently when editor crash or install/upgrade a package that has no burst code will also still retrigger burst compile. Not to mention when build game runtime, burst compile also takes most the time like 30+ mins at my laptop even I just change 1, 2 line of code I think.
Hi @optimise (good user handle by the way :)) - which version of Burst are you using? In Burst 1.8, players builds are now incrementally cached, so that if you only 1 or 2 lines of code, that player build should be much faster than the initial player build. I’d be interested to hear your experience with that, once you’ve tried it out.
There is a known issue where the cache isn’t persisted if the Editor crashes, and we’ll try to improve that.
After installing/upgrading a package, only the new or changed code should be (re-)compiled. Unaffected code won’t be recompiled, and the cached version will be used.
I’m using latest burst 1.8.2. Not sure whether it’s platform specific but when building android player runtime seems like will always take like 30+ mins even only change 1 or 2 lines of code.
Weird. Now I can’t reproduce retrigger burst compile when I install / upgrade package. Not sure whether it needs to trigger it at specific condition or maybe I’m using older burst version last time.