After some time messing with the ECS/Job system package, I hit some "problems" which are kinda annyoing the work with.
As I am building my project around ENet with a dedicated thread for network I/O and maybe one other thread on top of that for other coarse-grained tasks, I begin to see the need for a possibility to limit the used cores/threadnumber server-side for each running unity headless instance.
Right now I am testing my project on a 4C/8T CPU and I really would like to have two server instances running, using two Cores each. But with how the job system is working at the moment, it is having those instances fighting for free cores instead of having pre-defined reliable ressources.
Solutions for this problem:
1. It would be really useful to be able to set the amount of used cores/max threads for each project.
2. The possibility to check which cores are free to bind to (if job system worker threads are bound to logical threads).
3. Having an API to differ coarse-grained jobs from fine-grained operations.