ctuning / ck-wa Goto Github PK

Hi,

Suppose I run ck crowdbench wa:dhrystone [email protected] and have a WA issue. E.g. this one:

    * tmp-output2.tmp

  INFO     Removing existing output directory.
  INFO     Creating output directory.
  INFO     Initializing
  INFO     Running workloads
  INFO     Connecting to device
  CRITICAL ANDROID_HOME (/usr/local) does not appear to have valid Android SDK install (cannot find build-tools)

So, instead of parsing and displaying the actual error (the message after 'CRITICAL'), CK-WA says this:

Loading results.json ...
  (post processing script failed: /Users/dsavenko/CK/local/wa-result/2b692428a8a4b30a/20161017-154648/wa-output/results.json was not produced - program execution likely failed!)
***************************************************************************************
Pipeline failed (execution failed - /Users/dsavenko/CK/local/wa-result/2b692428a8a4b30a/20161017-154648/wa-output/results.json was not produced - program execution likely failed)!
***************************************************************************************

Need to check and fix.

I will create wa-scenarios module for CK-WA to pre-set various device and workload parameters such as

• cpu utilization
• fps
• markers api

I will add scenarios field to dashboard too ...

If scenario is needed, I will add the following flag to run wa:
$ ck run wa:youtube --scenario=fps

Reported by Michael McGeagh - checking now ...

We are developing crowd-benchmarking and crowd-tuning for Caffe and other DNN frameworks at http://github.com/dividiti/ck-caffe

Soon we will release an Android app to let volunteers collaboratively optimize various DNN workloads on mobile devices and should add this APK to WA ...

In the future, we need to collect, unify and record the following metrics (either via WA or CK or both):

· Current CPU Frequency over time (Overall, per cluster, per core)
· As above but for GPU
· Current Thermals over time
· Current Battery level over time
· Current memory usage

If WA was not yet installed and a user attempts to register target machine with WA, it will fail. We just need to add WA dependency to 'machine' module to solve it ...