Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add competition benchmarks for random/world component access #329

Closed
mlange-42 opened this issue Jan 13, 2024 · 8 comments · Fixed by #462
Closed

Add competition benchmarks for random/world component access #329

mlange-42 opened this issue Jan 13, 2024 · 8 comments · Fixed by #462
Labels
good first issue Good for newcomers tests Tests, benchmarks and profiling

Comments

@mlange-42
Copy link
Owner

Add benchmarks ECS performance comparison for access to components via the world instead of queries (i.e. by entity ID).

@mlange-42 mlange-42 added the tests Tests, benchmarks and profiling label Jan 13, 2024
@mlange-42 mlange-42 added the good first issue Good for newcomers label Feb 9, 2024
@captkirk88
Copy link

I don't recommend this. Arche will be smoked.

Just saying..

@mlange-42
Copy link
Owner Author

@captkirk88 Why do you think so, and compared to which ECS implementation?

@captkirk88
Copy link

captkirk88 commented Jan 3, 2025

@mlange-42 Are we talking any language? Or just C#?

@mlange-42
Copy link
Owner Author

@captkirk88 Arche is not in C#, it is in Go. To be fair and to make the proof easy, it should be Go. But I am not shy of comparing to other languages, too.

However, I would be more interested in what about Arche makes you think so.

@captkirk88
Copy link

If you are going to benchmark, then compare across all languages, not just Go. I mentioned C# because it isn't going to win. That's a given. But a overall comparison would showcase the differences between the languages and allow a better picture. I'm just tired of all these comparisons between ECS frameworks always being the same language. It defeats the purpose.

@captkirk88
Copy link

It's not a pissing match. It should be a fair and complete comparison benchmark.

@mlange-42
Copy link
Owner Author

Would definitely appreciate such benchmarks, but this repo is not the place for that.

@mlange-42
Copy link
Owner Author

Random access benchmarks were added to go-ecs-benchmarks, see section Component random access.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
good first issue Good for newcomers tests Tests, benchmarks and profiling
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants