Skip to Content.
Sympa Menu

perfsonar-user - Re: [perfsonar-user] running many test at the same time

Subject: perfSONAR User Q&A and Other Discussion

List archive

Re: [perfsonar-user] running many test at the same time


Chronological Thread 
  • From: Mark Feit <>
  • To: "Suchodolski, Adam" <>, "" <>
  • Subject: Re: [perfsonar-user] running many test at the same time
  • Date: Thu, 17 Oct 2019 14:08:35 +0000
  • Msip_labels: MSIP_Label_112e00b9-34e2-4b26-a577-af1fd0f9f7ee_Enabled=True; MSIP_Label_112e00b9-34e2-4b26-a577-af1fd0f9f7ee_SiteId=33440fc6-b7c7-412c-bb73-0e70b0198d5a; ; MSIP_Label_112e00b9-34e2-4b26-a577-af1fd0f9f7ee_SetDate=2019-10-17T12:03:07.5027149Z; MSIP_Label_112e00b9-34e2-4b26-a577-af1fd0f9f7ee_Name=Atos For Internal Use; MSIP_Label_112e00b9-34e2-4b26-a577-af1fd0f9f7ee_Application=Microsoft Azure Information Protection; MSIP_Label_112e00b9-34e2-4b26-a577-af1fd0f9f7ee_ActionId=00cda818-46ec-49bc-a709-3dad529422ea; MSIP_Label_112e00b9-34e2-4b26-a577-af1fd0f9f7ee_Extended_MSFT_Method=Automatic; MSIP_Label_e463cba9-5f6c-478d-9329-7b2295e4e8ed_Enabled=True; MSIP_Label_e463cba9-5f6c-478d-9329-7b2295e4e8ed_SiteId=33440fc6-b7c7-412c-bb73-0e70b0198d5a; ; MSIP_Label_e463cba9-5f6c-478d-9329-7b2295e4e8ed_SetDate=2019-10-17T12:03:07.5027149Z; MSIP_Label_e463cba9-5f6c-478d-9329-7b2295e4e8ed_Name=Atos For Internal Use - All Employees; MSIP_Label_e463cba9-5f6c-478d-9329-7b2295e4e8ed_Application=Microsoft Azure Information Protection; MSIP_Label_e463cba9-5f6c-478d-9329-7b2295e4e8ed_ActionId=00cda818-46ec-49bc-a709-3dad529422ea; MSIP_Label_e463cba9-5f6c-478d-9329-7b2295e4e8ed_Parent=112e00b9-34e2-4b26-a577-af1fd0f9f7ee; MSIP_Label_e463cba9-5f6c-478d-9329-7b2295e4e8ed_Extended_MSFT_Method=Automatic

Suchodolski, Adam writes:

 

I need start more than one throughput test at the same time to simulate real like network load.

I’ve tried change test classification in “enumerate” file but that’s not enough.

Pscheduler schedules the throughput test 19 s later after a previous one (example command submitted two times to schedule two tests at one time: pscheduler task --url --start=2019-10-16T14:03:00Z throughput --dest 192.168.43.67).

 

That is correct.  Scheduling a throughput test requires cooperation from both ends, and if one end still thinks it shouldn’t run two throughput tests at once, it’s only going to offer times that it thinks are eligible.

 

I can’t put this in bold-enough type, but I do not recommend changing the scheduling class of existing tests.  There are reasons throughput is classed exclusive, most of which have to do with producing accurate measurements.  If other institutions run tests against your systems without knowing you’ve done this and understanding the ramifications, they run the risk of making decisions based on distorted data.  The disclaimer here is that if you break something, you own both pieces.

 

The proper solution would be to identify tools that are capable of doing bidirectional throughput testing and writing integrating them with pScheduler by writing plugins.  You’re not the first to mention it, but we haven’t had enough demand to devote project resources to it.  (We do welcome outside help.)

 

--Mark




Archive powered by MHonArc 2.6.19.

Top of Page