From: Perry Gagne pgagne@redhat.com
Turns out if neper doesn't have the response size definied on the server side, it defaults to 1, instead of whatever the client param is.
Signed-off-by: Perry Gagne pgagne@redhat.com --- lnst/RecipeCommon/Perf/Measurements/NeperFlowMeasurement.py | 4 ++++ 1 file changed, 4 insertions(+)
diff --git a/lnst/RecipeCommon/Perf/Measurements/NeperFlowMeasurement.py b/lnst/RecipeCommon/Perf/Measurements/NeperFlowMeasurement.py index 84a00c16..6976547d 100644 --- a/lnst/RecipeCommon/Perf/Measurements/NeperFlowMeasurement.py +++ b/lnst/RecipeCommon/Perf/Measurements/NeperFlowMeasurement.py @@ -78,6 +78,10 @@ class NeperFlowMeasurement(BaseFlowMeasurement): elif flow.cpupin is not None: raise RecipeError("Negative perf cpupin value provided.")
+ if flow.msg_size: + server_params["request_size"] = flow.msg_size + server_params["response_size"] = flow.msg_size + return host.prepare_job(NeperServer(**server_params), job_level=ResultLevel.NORMAL)