I took a quick look at the documentation but I can’t find anything about ECS implementation of Xenko. Can you link me the relevant parts of the documentation?
however, i have a question here for @xen2:
how does the xenko entity component system relate to the new ways of dealing with composition and multi threading as described here in the unity intro videos? what they are doing is basically laying the data out in a cache friendly way and then run parallelized jobs on it. is this already possible in the xenko engine, or how does it relate to xenkos approach to multi threading?
What we don’t have yet is cache localized data, and maybe it could be reorganized better to be job friendly.
However, cache localized array is something we already do in the RenderFeature layer, and the idea was to do something similar for the ECS at some point (and rearchitecture some part of it to be more efficient).
I leave it here in case you are interested, but with Svelto.ECS my main goal is not just performance. I see adopting ECS as a shift of paradigm from Object Oriented Programming which let easily to write modular, testable and maintainable code. The github page links to all my articles in case you want to know more.
Just to clarify a bit Kryptos’ latest reply as people have been mis-interpreting it on Discord, he is referring to ‘Aman_Deep’'s reply (as you can see on the upper-right of that reply), which was removed from this thread, not tonfilm/tebjan’s unity video.