Portable and Predictable Performance on Heterogeneous Embedded Manycores (ARTEMIS ) ARTEMIS 2 nd Project Review October 2014 WP2 “Application use cases” (Presented by: Tapio Taipale) ARTEMIS PaPP Review 20141

WP2 “Application use cases” Specification and development of use-case applications. Use cases have been re-arranged in order to comply with WP6 demonstrators 1. Multimedia BUT, CAMEA, HIB 2. Space SSF, TAS-E, Tecnalia(*) 3. Mobile communications EXFO (*) Tecnalia’s has withdrawn their own use cases and concentrate their effort to TAS-E use case ARTEMIS PaPP Review 20142

WP2 Objectives 1.Specification of the use case applications based on industrial requirements 2.Implementation of parallel versions of applications using methods and tools developed in WP3 and WP4 3.Specification of evaluation strategy and metrics ensuring large test coverage Because of its crucial position in the project, WP2 also has strong collaboration objectives. Industrials will provide constant feedback to tool developers and provide them with required test material ARTEMIS PaPP Review 20143

WP2 Objectives for Y2 1.Final version of use case specifications Applications characteristics (specifications) and the most significant technical and non-technical industrial requirements 2.Intermediate use case implementations First versions of use cases using tools, methods and platforms from WP3, WP4 and WP5 3.Updated evaluation plan and complete evaluation strategy The evaluation criteria on which all partners will agree ARTEMIS PaPP Review 20144

Task 2.1: Specs and reqs for use cases Objective: “Specification of the use case applications based on industrial requirements” Use cases: Multimedia domain: use cases by CAMEA/BUT, Tecnalia and HIB Space domain: use cases by SSF and TAS-E Mobile Communications domain: two use cases by EXFO Task output: deliverable “D2.4 Final Version of Use Case Specifications and Requirements” Deliverable still lists Tecnalia use case because deliverable was submitted in the middle of the 2 nd year and use case was withdrawn shortly after that HIB uses cases were still described as separate use cases ARTEMIS PaPP Review 20145

Task 2.2: Implementation of use cases Objective “Implementation of parallel versions of applications using methods and tools developed in WP3 and WP4” Total of six use cases presented Tecnalia use case withdrawn HIB use cases combined into one use case Task output: deliverable “D2.6 Intermediate use case implementations” ARTEMIS PaPP Review 20146

Use case implementation status Use case (*) PartnerUse case appStatus after Y2Expected improvements in Y3 2.1CAMEA / BUT Radar-based Object Detection for Traffic Monitoring Ported to FPGA, single-core ASIP and on virtual multi-core platform. On 6-core PC platform, gained 4.7 x speed-up with parallel loop optimization using OpenMP pragmas. Porting to multi-core ASIP. Transforming application using OpenMP task-based programming model. 2.3HIBMobile Surveillance Runs on Android emulator and devices. Adaptivity based on energy consumption introduced. Porting to Parallella board. Parallelization of OpenCV and Ffmpeg libraries in cooperation with PaPP partners. 3.1SSFSpacecraft Instrument Data Processing SW Runs on a Linux Workstation and PaPP HW emulator. Use case ported on PaPP SW stack and builds with PaPP tool chain. Parallelization using PaPP OpenMP task- based programming model. Analyzing application on single and multi- core platforms with PaPP profiling tools. 3.2TAS-ELossless data compression Runs on Linux and Windows. First part of the application, compression, parallelized using OpenMP. Parallelization of the second part. Porting to Leon architecture. 4.1EXFOFlow analysisRuns on the Linux. Profiled with PaPP utilities in multi- core environment. Application of new application framework and parallelization through it. More in-depth analysis with PaPP tools. 4.2EXFOCall and session analysis Runs on the Linux platform and PaPP virtual environment. New application framework taken into use. Profiled with PaPP utilities. Iterative parallelization of application framework using OpenMP task-based programming model. More in-depth analysis with PaPP tools ARTEMIS PaPP Review (*) Numbering refers to the chapters in the deliverable D2.6

Use case vs PaPP Use case (*) PartnerUse case appWP3WP4WP5Source code available in PaPP repository 2.1CAMEA / BUT Radar-based Object Detection for Traffic Monitoring Optimization in cooperation Ported on PaPP virtual environment. Yes 2.3HIBMobile Surveillance Optimization in cooperation. Ported on PaPP virtual environment. Porting on Parallella board in Y3. No 3.1SSFSpacecraft Instrument Data Processing SW Builds with PaPP tool chain. Ported on PaPP virtual environment Yes 3.2TAS-ELossless data compression Parallelization using OpenMP in cooperation. Ported on PaPP virtual environment. Yes 4.1EXFOFlow analysisProfiling in cooperation. --No 4.2EXFOCall and session analysis Profiling in cooperation. Ported on PaPP virtual environment No ARTEMIS PaPP Review (*) Numbering refers to the chapters in the deliverable D2.6

Task 2.3: Specification of evaluation criteria Objective “Specification of evaluation strategy and metrics ensuring large test coverage” Participants have updated the evaluation criteria against which the progress of PaPP will be measured. Task output: deliverable “D2.5 Updated evaluation plan and complete evaluation strategy” ARTEMIS PaPP Review 20149

PaPP objectives: criteria & evaluation PO 1: Efficient and accurate performance models of applications executing on computational platforms. Success criteria: The models can capture performance of an application executing on a new platform within a factor of 15% given enough information about architecture and application. Evaluation: How the performance has been improved per se and compared to prediction models Radar-based object detection and Image data compression use cases have reported performance improvements for parallellized versions of the use case applications ARTEMIS PaPP Review

PaPP objectives: criteria & evaluation PO 2: Portability of performance across at least two hardware platforms for the application use cases. Success criteria: The methodology and tools developed in the project have been used to demonstrate that for the application use-cases portable performance as predicted by the performance models is achieved. Evaluation: At least one of the demonstrators (Multimedia) will have its composing use cases compiled and tested for two different architectures and performance compared via valgrind profiling (see D2.4) and the associated metrics ARTEMIS PaPP Review

PaPP objectives: criteria & evaluation PO 3: Portability of the software stack across application domains. Success criteria: The PaPP software stack has been used across at least two application domains in its entirety. Evaluation: The three different demonstrators (Multimedia, Space and Mobile Communications) use different architectures (ARM, SPARC andx86) and the usage of the toolchain is envisaged for all of them ARTEMIS PaPP Review

PaPP objectives: criteria & evaluation PO 4: Software developer productivity is increased. Success criteria: PaPP methodology and tools are used to reduce development time as perceived by application use- case providers. Evaluation: The main measures for this criteria will be establishing a baseline for one developer using non-PaPP tools for a given task and then repeating with a PaPP-aware developer. Variablity tool applied in Mobile Surveillance use case has reported effort decrease in build and configuration task In Image data compression use case, usage of OpenMP has increased productivity ARTEMIS PaPP Review

PaPP objectives: criteria & evaluation SO 1: Improved resource management. Success criteria not defined Evaluation: Mobile surveillance has applied successfully PaPP adaptability approach on the energy management. Energy awareness and management is also a topic of interest for Radar- based object detection use case which also deals with battery-driven devices ARTEMIS PaPP Review

PaPP objectives: criteria & evaluation SO 2: The ability to create reusable parallel software components, both domain specific and domain independent. Success criteria not defined Evaluation: Software components used in the Multimedia and Mobile Communications Use Cases are expected to make their way into commercial tools. Effort will be put into the reusability aspects of these and it will be investigated how using such components affect the larger systems which may not be using PaPP ARTEMIS PaPP Review

WP2 Cooperation Periodic telcos within WP2 Deliverable preparations Issue handling related to other WP tools ARTEMIS PaPP Review

WP2 Objectives for Y3 Final use case implementations Delivery of the final versions of the use case prototypes to partners with an implementation report which also provides updated information from D2.6. Deliverable D2.7 due on M36 (end of Aug, 2015) ARTEMIS PaPP Review

Plans to achieve Y3 objectives Increase cooperation Between work packages Participation of other WPs in WP2 meetings in order to transfer information about use cases and their requirements to WPs responsible for PaPP methods and tools Between WP2 participants In order to unify use case descriptions and feedback to other WPs Tighter cooperation improves quality of deliverables Ensure progress and also cooperation Periodic meetings throughout the year Not just for deliverable preparation For ensuring that communication between WP participants is working ARTEMIS PaPP Review