jobs/fxmark.yaml: split different thread parameters

If the thread_nr parameter is not set explicitly, fxmark will run
several rounds of tests in one job with different thread_nr value.
This may have some potential issues:

* We cannot know the monitor data is recorded in the period of which
thread value.

* The test under some specific thread value (such as 36 threads) may
have tricky disk space contention issue that may produce unstable or
invalid result.

Suggested-by: Feng Tang <[email protected]>
Signed-off-by: Yujie Liu <[email protected]>
Signed-off-by: Philip Li <[email protected]>

Author: Yujie-Liu

jobs/fxmark.yaml

@@ -40,3 +40,11 @@ fxmark:
   directio:
     - bufferedio
     - directio
+  thread_nr:
+    # - 1
+    # - 2
+    - 4
+    - 18
+    # - 36 # may have disk space contention issue
+    - 54
+    # - 72