Significant performance hit after upgrading to 2022 (burst)

Did significant changes to burst compiler or to jobs? Most of my burst compiled jobs in 2021.2.17f are ~10x slower in 2022;
No package or code changes.

2021:

2022:

Edit:
Tried upgrading burst to 1.7.1 and deleting the library folder (helped me in the past with burst bugs), still slow.

1 Like

It maybe because, DOTS packages are not ready for 2022.

I mean, it wasn’t ready for 2021 either :smile:. But you are right.

A bit worried however, since entities has a lot of problems in 2021 and I’m expecting 0.51 to be released only for 2022 at this point.

That scared me a bit. I’ll ask stupid question, are you comparing performance with disabled safety checks and enabled synchronous compilation? Are you using Jobs or BurstCompiler.CompileFunctionPointer?

0.51 is aimed for supporting 2021.
1.0 is aimed for supporting 2022.
None of these are released yet.
Expecting breaking changes, if trying to push packages to these Unity versions.

However, DOTS packages in general are not even officially supporting 2021. Many did hack packages, to make it compatible with 2021.

1 Like

Synchronous compilation ON, safety check OFF
Leak detection and jobs debugger OFF (if it matters)
I only use jobs no function pointers

That said, I’m back with 2021. I wasn’t expecting any changes with 2022 tho.

I’m curious, is this Entities.ForEach job or user defined job struct? Also is it parallel job?

1 Like

Jobs and Burst should work fine in 2022, so please file a bug (but only those features, as they aren’t depending on the rest of dots like entities).

So if you are not using entities it would be a valid bug I think?