Question MeshCollider.Create benchmarks

MeshCollider.Create is taking 25ms on 3500 vertices.
Physics 1.0.10 with Burst enabled and safety checks off.

Is this as fast as it gets? appreciate any optimization tips?

Project and benchmark code here.

 

If you intentionally build compound of quads instead of using MeshCollider directly, then at least you could spread quads creation over multiple threads by using IJobFor instead of IJob. After that the CompundCollider.Create has to be moved into a job too (I believe it's not bursted when used in the managed context), that depends on the first one, i.e. job2.Schedule(job1.ScheduleParallel(triangles.Length / 2, quadsBatch, default)).Complete().

 

The meshcollider.create performance is a known issue, there was a thread open about it with some benchmarks and more years ago: https://forum.unity.com/threads/uni...parameters-to-disable-internal-checks.776402/