Burst, Jobs in WebGL build

Hi There
What is the state of Jobs and Burst in a WebGL build? Should it be running the same speed as you get in a standalone PC build? When I build my test project for standalone it runs fine, hundreds of FPS using Jobs and Burst for some complex processing, but the same build for WebGL runs really slowly. I have the project settings set the same for both so Burst and Jobs should be compiled just the same. Am I missing some setting, or do Jobs and Burst just not work well in WebGL builds?

 

Hello, Burst should be fine in WebGL build but multithreading support in Web browser is not "mainstream" yet.
So you most likely don't run jobs in your WebGL build.

 

How about interfacing with JS-Webworkers?

 

I think it's the plan but last I tried a few month ago it required manually activating some things in the browser which is not ideal in term of end user experience.

I'm actually amazed the OP project worked. Mine simply failed when having any schedule in my code. Maybe Unity did something in the build pipeline for web gl to replace schedule by run?

 

Here's an exampulatory WebGL-project that I have that runs with Burst + Jobs:
https://quakeulf.itch.io/chairs

It's of course singlethreaded as of now if what is being stated is correct, but the object generation/manipulation is all done using the Job System.

 

If you build on Windows. And have not set this:
JobsUtility.JobWorkerCount = 5;
JobWorkerCount will be auto.

If you build on WebGL.
JobWorkerCount default 0, And it must be 0 .

So, same code, WebGL more slower. (Just single thread)

 

starock2020 where do you set JobWorkerCount in code?