[Scummvm-devel] Bi-annual ScummVM binary size email

[Max Horn]

Hi Angus, all,

Am 06.10.2010 um 03:08 schrieb Angus Lees:

> On Wed, Oct 6, 2010 at 07:25, Max Horn <max at quendi.de> wrote:
>> Definitely would be worth it. In the best of all worlds, we could even automate it and run it as part of our buildbot with the nightlies (or even with all builds). We could then even graph the size changes for each engine over time, which would help pin-pointing particular bad cases of code size increase ...
> 
> In fact if you graph it often enough, you won't need to generate the
> other more detailed information described in this thread.  Given the
> time correlation, it should be quite easy to spot steps in the size
> graph and then bisect the exact commit that introduced it...

Excellent point! We don't get one build per commit, but close enough to usually being able to pinpoint the increase to a certain day is good enough.

So, we could enhance our buildbot code to record the size of certain files (e.g. the NDS binary, but also others, of course) after each build. These data tuples (binary size, date, revision being built, ...) should then be put into a database (well, or a textfile, but a real DB might be easiest and safest. It should be easy to use an SQLite database from Python).

Then, another script could generate (possibly dynamically, e.g. a PHP script) a webpage with a graph plotting that data. 

All in all, this doesn't sound too difficult. Just "somebody" would have to do it :).

Cheers,
Max