Large speed difference between editor and standalone player when using BURST

I have been racking my brain with this. I am generating a large map. Everything is setup with Jobs and Burst and on the Editor I can build my map in about 20 seconds. When I build the standalone player and run that building the same size map it takes around 120 seconds. It does appear that the burst generated .dll is being produced.

Using Unity 2020.3.2f1.

My Player settings seem correct.

Any help would be appreciated.

 

Are you building with the building configurations from the samples ?

 

Hey Thanks for responding. Could you elaborate a little regarding the "building configurations from the samples"? Not quite understanding what that is.

Thanks!

 

Sure here they are, copy to your project, select the one you want to build and in the inspector you will see a build button.

https://github.com/Unity-Technologi.../master/ECSSamples/Assets/BuildConfigurations

 

If I understand you correctly I am using the PC, Mac, & Linux Standalone.

 

I've done a few tests recently exporting Burst-jobs to various platforms to see how they perform. When building a mesh with a million vertices I seem to get better performance outside of Unity. There could be a lot of variables involved here if it is a complex setup. I just use the default settings (Windows Standalone).

 

I have timings throughout my execution so I was able to analyze that:

Editor Timings:

Summary:
Some of my time stamps are as good or better from the editor to the .exe. Some of them are WAY slower. I double checked with the jobs in those timing segments. It seems like the jobs where I tried to use generics with were the culprits.

For example:

Code (CSharp):

1. [BurstCompile(CompileSynchronously = true)]
2. public struct GenerateHeightMap<T> : IJobParallelFor where T : struct, WorldGenNoiseStructInterface
3. {
4.     [ReadOnly]
5.     public NativeArray<TilePositionDataStruct> TilePosData;
6.     [ReadOnly]
7.     public NativeArray<float2> VerticeLoadout;
8.  
9.     public int VertSize;
10.  
11.     [ReadOnly]
12.     public T NoiseFunction;
13.     [ReadOnly]
14.     public NativeHashMap<NoiseOctaveIndex, NoiseConfigData> NoiseConfigs;
15.  
16.     //Output
17.     public NativeArray<float> Heights;

So this is the issue. These job structures are performing as expected in the editor but not in the exe. Any thoughts would be appreciated.

 

Furthermore the function GenerateHeightMap is not showing up in the Burst Inspector within the editor nor is it showing up in the lib_burst_generated.txt file of the .exe compilation

 

First idea would be that burst JIT compiles the generic job type when it is used in the editor, but it can't statically determine which generic version to precompile for a build (if it could, it'd show up in the inspector) - so it runs managed instead?

Do you explicitly use GenerateHeightMap<something> where something is an actual type, or is it 'nested' generics?

 

Thanks guys. This does appear to be my issue. I should have read this in the manual. Looks like I have some re-architecting to do.