perfsonar / perfsonar/docs

Incorrect statement in the FAQ

Open
#205 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

correction docs.perfsonar.net review needed
Dominant language
Python
Stars
5
Forks
7
Avg merge
1m
Merged PRs (30d)
1

Description

http://docs.perfsonar.net/FAQ.html#q-can-i-run-both-throughput-and-latency-loss-tests-on-the-same-interface-without-interference-due-to-the-way-pscheduler-scheduling-works

A: Currently you cannot guarantee no interference. pScheduler rtt test that execute the ping tool and OWAMP latency and latencybg tests that execute owping and powstream respectively, are considered background tasks and can be scheduled in parallel to each other as well as throughput tests. Given the frequency with which users prefer to run tools such as ping and owping (and powstream runs constantly), there would be very few tests slots available if this were not the case. This does not mean you cannot run these tests on the same interface, it just means some correlation of results may be necessary when debugging. It is recommended, though not required, you run these tests on separate interfaces from throughput.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Open the FAQ entry at the linked docs.perfsonar.net URL and compare the existing answer with the issue body. Update the inaccurate wording about pScheduler RTT, OWAMP, owping, powstream, and throughput tests, then verify the rendered FAQ entry communicates the intended scheduling and interference guidance.

Written by the indexing model from the issue text.

Assessment

Domain
documentation
Issue type
Documentation
Difficulty
1/5
Estimated time
Under an hour
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.