LAVA and Android Toolchain Benchmarks
zygmunt.krynicki at linaro.org
Wed Jan 18 11:16:13 UTC 2012
Hi, looks nice :)
On Wed, Jan 18, 2012 at 5:59 AM, Andy Doan <andy.doan at linaro.org> wrote:
> Sorry for the wide distribution, but I wasn't sure who all would be
> I spent time over the last month updating the Android monthly toolchain
> benchmark process to pull its benchmark data from LAVA tests that are
> stored in validation.linaro.org. Here's an example test run.
> This month's results will be published to the wiki as I normally do.
> However, I spent some time last weekend looking at how to handle this on
> the validation server as well. I first toyed with trying to do a simple
> report plugin. However, it really didn't quite have everything I thought
> was needed.
> I wound up using the "LAVA kernel CI views" project as a skeleton to
> create something for Android. I've got a local prototype that's starting
> to do just about everything I want (I'm fighting some issues the the
> you can get a rough idea.
> Before I really invest time, I wanted to get people's thoughts. Some big
> questions for me:
> 1) Is anyone against doing this?
That's a question to TSC (regarding benchmark data)
> 2) The project is currently called "Android Benchmarks". However, I'm
> wondering if we should make more of a generic view for "Android".
> "Toolchain Benchmarks" could then be one part of this, but we'd have a
> spot to add other things if needed/wanted. Due to how projects are shown
> across the top of validation.l.o, I think we need pretty concise entries.
Would you mind sharing the source code with the validation team? I
want to see what models/views you have.
Last weekend I created lp:~zkrynicki/+junk/lava-android. Perhaps it
would make sense to meld both extensions and have one "android insight
As for the top-level menu it's going to change entirely (one day, when
we have the time to rework that part) into a "Projects,
Infrastructure, Me" menu. Most of the low-level pieces will be in the
infrastructure menu. Projects will grow an ability to pull in pieces
of infrastructure that are related to that project (say daily
builds/tests/benchmarks) while the me-menu will have stuff the user is
participating in/associated with/etc. So don't worry about the menu,
we'll manage that part soon enough.
> 3) If the general thought is "this looks okay", then are you guys okay
> with targeting it for next month?
More information about the linaro-android