Re: SVC on Gepop with BBQ

[Patrick Bellasi]

On Mon, Apr 15, 2013 at 2:59 PM, Jens Brandenburg <jens.bra...@hhi.fraunhofer.de> wrote:

I think both sources and a binary package can be delivered.

The Binary package could be easily distrbuted as an update.zip, which could be automatically generated by the BOSP building system out of the <BOSP>/out/ folder contents.

Than the deployment instructions are straightforward:

1. start GePOP the usual way

2. run an update script to deploy all SW components

3. run a provided demo script, which has been packaged with SW modules and thus deployed in the previous step.

Yes all forms of SVC scalability are possible at runtime, meaning you can change the resolution, the frame-rate and the image quality. All three types of scalability will have an impact on the execution time.

To better asses the scenario we need some really preliminary numbers related to the average execution time on GePop ARM+ISS to decode a single frame in 2 or 3 different configurations... could you provided these numbers Jens?

Any kind of help is appreciated. I am not sure if I understand your scenario fully. Maybe you can specify the scenario more in detail. Please remember one instance of an SVC decoder will use max all pe's of one cluster only (or the other way around one instance of an SVC decoder will not use multiple clusters).

Roughly:

1. start SVC1, the high priority instance

2. start SVC2, the low priority instance

3. after a while: reduce the power budget by using the BBQ provided interface

have a look to this video to get an idea: http://www.youtube.com/watch?v=oaa6I1IVA8w

=> we expect that BBQ will re-schedule resources to keep in pace with the reduce power budget, thus:

4. SVC2 should be switched to a lower AWM, which is expected to use less power, while SVC1 should not be touched, since it's an High Priority application

5. after a while: reset the power budget... we expect SVC2 being re-scheduled in the high performances working mode.

NOTE: priorities are defined by the recipe used, thus you should add a command line parameter which allows to select the high or low prio recipe for the specific instance.

 

Furthermore I need help in collecting the power metrics. I can also provide you the code, to enable you to perform measurements by yourself.

BarbequeRTRM has already the required support to collect and plot power metrics, as you could see on the previous video. You just need to run the application with the most recent version of BBQ-sthorm branch... and than, in a console, run the script:

<BOSP>/out/sbin/bbque-plotpower-sthorm

Ciao Patrick

--
#include <best/regards.h>

Patrick Bellasi
Post-Doc at Politecnico di Milano
http://home.dei.polimi.it/bellasi