ecs_benchmark VS ecs_benchmark

So far, I've used this as a direct comparison: it's Flecs (I think it needs no introduction), and it's implemented in C

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.

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.