perfSONAR User Q&A and Other Discussion

[Mark Feit <>]

Murilo Vetter writes:

 

One thing that I was thinking about is that in our scenario, we are deleting file: /etc/pscheduler/limits.conf

The purpose of that was to bypass some limitations imposed by default restrictions.

 

Removing the limit configuration disables the limit system entirely and will allow any requester to do anything.  It would be better to adjust the existing configuration to allow the things that are being restricted.  Ivan posted a link to the docs, and there’s a seminar on our YouTube channel called Know Your Limits that might be helpful.

 

We would like to run long time period tests. In the past, we already run this kind of test invoking directly iperf3 tool.

Do you think could it interfere in anything?

 

If you’re running pScheduler on the same system, yes.  The throughput plugin tells pScheduler to give it exclusive use of the system (aside from background tasks) to avoid contention for network bandwidth and machine resources that can distort the results.  Running iperf3 behind pScheduler’s back subverts that.  Because the iperf3 plugin uses the default port, you may see run failures or other unexpected behavior if pScheduler tries to schedule a run at the same time.

 

pScheduler will be able to handle very long runs once the bug in ticket #945 has been resolved.

 

--Mark