Benchmarks

[olls]

@TiberiumPY

Things like render time and terrain generation speed.

@olls but for pypy you don't want to use cProfile..
I'll change it to profile myself.

[olls]

I'm not sure what you mean, I'm using the timeit module.

[olls]

Use environment variable PYCRAFT_BENCHMARKS=True to enable timings, then also use PYCRAFT_LOGGING_MODES=\[\"benchmarks\"\]

@olls
cProfile.runctx('game(server_obj, settings, render_c, benchmarks)', globals(), locals(), filename='game.profile')
or it's only for C module?

[olls]

The cProfile part was already there. See my last comment to enable the timeit timings.

@olls ah, ok

[olls]

On my machine I get around 0.05 seconds with python renderer, and 0.015 seconds with the C renderer. Which is promising, as there is a lot more space for optimisations in the C.

@olls and where's resulting log will be located?

[olls]

The results are output to pycraft.log, the easiest way to view them is to run tail -f pycraft.log in a second terminal side by side with Pycraft.

[olls]

We'll document all this at some point...

@olls I get render call time ~0.003 seconds
On CPython 3.5 with C module:
0.0025 - 0.0015

So PyPy is actually not that slow compared to C

But PyPy3 is not that well optimized as PyPy2 is

[olls]

So the 0.003 time was with PyPy?