Engine Testing - 97.0.1-425-g3d34d8b (23. Sept 2014)

[Silentwings]

How would I point out which parts are slower? Give me a detailed method for doing so and I will do that.

I would guess that the amount of changes (since 91.0) makes this nearly impossible and bisection would be the only way. But, on a related note, I would be interested to see an updated version of http://springrts.com/phpbb/download/file.php?id=7567 for an intense 98.0 game. I would make one myself but my self-compiled Spring seems not suitable for profiling.

This thread is now off-topic since 98.0 exists

[Google_Frog]

Bisection is not feasible because:

• There are periods where Spring did not compile or crashed frequently.
• Apparently other performance issues are responsible for poor performance in earlier versions. Such as PFS update rate (which jK seems to have fixed) and drawing decals twice.
• Performance with 94.1 was really bad and it has slowly improved since.
• ZK is probably incompatible with anything except 91.0 and recent dev versions.

I would be interested to see an updated version of download/file.php?id=7567 for an intense 98.0 game.

That seems like a profiler with very useful information. Would anyone be able to generate one or set up an easy way for me to generate one? Ideally something like that would be activatable from ZKL so players with performance problems can give useful feedback.

[abma]

Bisection is not feasible because:

i meant bisecting by disabling engine features (if possible), for example:
/luaui disable
/luarules disable

test with spring-headless, etc.etc. :D