Benchmark time consumption issue 

We have a timeout problem with benchmarks on our slow devices (Android, Raspberry Pi, iOS). In our current automatic benchmark setup we've set a timeout at 30 minutes, but these devices cannot finish in that time.
After i removed the 512 symbols, the faster android devices are able to finish. However, the raspberry pi and android 2.3 is not.

I don't know if this a problem with gauge's iteration calculator, buildbot, or the kodo benchmarks? In my opinion I think that we should try to aim at getting the the benchmark time down rather then increasing the timeout.