Minor fix of compute QPI spec

- align terminology with project FAQ[1]
- use different weight in sections

[1]: https://wiki.opnfv.org/display/qtip/FAQ#FAQ-Algorithm

Change-Id: I1161c333584952dfa9d23be3010f572d4b315b60
Signed-off-by: Yujun Zhang <zhang.yujunz@zte.com.cn>

diff --git a/benchmarks/suite/compute.yaml b/benchmarks/suite/compute.yaml
index f95d4ac..0761a87 100644 (file)
--- a/benchmarks/suite/compute.yaml
+++ b/benchmarks/suite/compute.yaml
@@ -1,20 +1,20 @@
 QPI: compute
 description: sample performance index of computing
 
-algorithm: weighted-average
+algorithm: weighted arithmetic mean
 
 section:
 - name: Integer
-  weight: 0.2
-  algorithm: geometry-average
+  weight: 0.3
+  algorithm: geometric mean
   perftests:
     - name: dhrystone
       workloads:
         - single_cpu
         - multi_cpu
 - name: Floating
-  weight: 0.2
-  algorithm: geometry-average
+  weight: 0.3
+  algorithm: geometric mean
   perftests:
     - name: whetstone
       workloads:
@@ -22,23 +22,23 @@ section:
         - multi_cpu
 - name: Memory
   weight: 0.2
-  algorithm: geometry-average
+  algorithm: geometric mean
   perftests:
     - name: ramspeed
       workloads:
           - int: [add, average, copy, scale, triad]
           - float: [add, average, copy, scale, triad]
 - name: DPI
-  weight: 0.2
-  algorithm: geometry-average
+  weight: 0.1
+  algorithm: geometric mean
   perftests:
     - name: dpi
       workloads:
         - bps
         - pps
 - name: SSL
-  weight: 0.2
-  algorithm: geometry-average
+  weight: 0.1
+  algorithm: geometric mean
   perftests:
     - name: ssl
       workloads: