Convenience issue for testers to send their benchmark results.
Just drag and drop the txt or other output files in a new reply.
Inform the CPU where you ran the benchmarks in your reply. Simple id (like i7 6700k) is more than enough.
Prebuilt binaries can be downloaded here:
https://github.com/Alan-FGR/minECS/tree/entt_bench/Benchmarker/prebuilt
It's just a compiled distribution version of that branch.
native contains native binaries and thus don't require any runtime. Run the Benchmarker.exe.
bench contains managed binaries and require dotnet to run. There's a _run.bat for convenience.
Both versions require Win7+ 64 bit. Please inform which version you've used.
Thank you!
NOTE: in the detailed results, if you're using the managed version the first loop takes much longer because of jitting. It could be pre-jitted but I'm discarding those values that are too off so it doesn't affect the results_ALL
Convenience issue for testers to send their benchmark results.
Just drag and drop the txt or other output files in a new reply.
Inform the CPU where you ran the benchmarks in your reply. Simple id (like i7 6700k) is more than enough.
Prebuilt binaries can be downloaded here:
https://github.com/Alan-FGR/minECS/tree/entt_bench/Benchmarker/prebuilt
It's just a compiled distribution version of that branch.
nativecontains native binaries and thus don't require any runtime. Run the Benchmarker.exe.benchcontains managed binaries and requiredotnetto run. There's a_run.batfor convenience.Both versions require Win7+ 64 bit. Please inform which version you've used.
Thank you!
NOTE: in the detailed results, if you're using the managed version the first loop takes much longer because of jitting. It could be pre-jitted but I'm discarding those values that are too off so it doesn't affect the
results_ALL