#Hey o so I am doing some mesh generation

1 messages · Page 1 of 1 (latest)

brave girder
#

seems like both processes r blocked by the same race condition (the generation) so the performance should be around the same

fathom plover
#

Well the difference would be doing multiple loops vs a single one, and having multiple jobs that execute in order vs a single job that does it all.

#

It is doing the same work either way, so I think it would be about the same...

outer bridge
#

I can't see two jobs ever being faster than doing it in one job. Is this not a IJobParallelFor?

#

Best case scenario, it's a parallel job, which means the second job can begin processing vertices that are ready before the first job completely finishes, if there are worker threads available.

#

But even in that best case scenario, it still can't be faster than doing it all in the first job. Only just as fast.

fathom plover
#

I guess time to look in to seeing if you can use delegates with jobs. Or maybe just a native array of an interface... I don't think it supports that though. Otherwise I am going to have to put it all in one struct with a bunch of bool toggles and it is going to be real ugly.

fathom plover
#

I feel like there must be, because Entities must do something like this for its components

outer bridge