ecs_benchmark VS dominion-ecs-java

I guess he/she didn't (well, at least judging by the very chatty tone typical of the I would do it better devs), although someone did it for us already if you're interested (for EnTT and for many other libraries too).

As a benchmark, I am currently using Flecs, Legion and others like EnTT and all benchmarks are allocating data sequentially to get cache locality ... How could I not do the same? 😉

Yes, I've already taken a look at those benchmarks, and I'd say it looks like the Retinazer's overall performance is better than Artemis. At this moment, I'm comparing my performance progress against Flecs or other system language ECS like EnTT, which are considered the benchmark.

This is not a real benchmark, but if you could translate this to use your library, then that'd be a decent starting point. It's a few systems and components. The benchmark should be testing how fast you can update 1 million entities. The code in the playground link is based on this C++ ECS library comparison, specifically this file.

You are right, I will add more info about the architecture! About which operations perform better you can already relying on the available benchmarks

Check out the new Quick Start section to see the “how-to”.

Dominion aims to have a clean and minimal API surface and all the features already implemented are documented, tested, and with benchmarks. A simple example code has been provided in a dedicated module.

With this project, I aim to demonstrate that Java can also participate in the competition and for good reasons.

Dominion is still in its early stages but has already started running at a very high speed, fast by design. It's still far from a complete ECS solution, but I've already implemented the API to create/delete Entities with Components, find them and iterate. I've also posted some benchmarks related only to what I've achieved so far (so on the speed of creating, deleting, and iterating Entities), and I think it looks very promising.