perfsonar-user - RE: [perfsonar-user] High latency error
Subject: perfSONAR User Q&A and Other Discussion
List archive
- From: Danilo Berruto <>
- To: Mark Feit <>
- Cc: "" <>
- Subject: RE: [perfsonar-user] High latency error
- Date: Tue, 17 Mar 2020 08:59:42 +0000
- Arc-authentication-results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=eutelsat.com; dmarc=pass action=none header.from=eutelsat.com; dkim=pass header.d=eutelsat.com; arc=none
- Arc-message-signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=X6i4EkN8PI7fH6kEq3roRHhSTUvrqsj3j1DHoEPaNwc=; b=FSGkklZgCU8uNRLGHgFXxDvOYZG6twuWzKfjqDRJMKltzqjvzu3fBhJqvl0f+dPxMgqPAwvcrkFpeYPMRtE28vpT0gBWWhchSz1jwfh1fZZe0LJrg1P4nCsg6K8PBVm1P7ELczbpSou1piLstQKJRABvr2jT9fxOAyiawWxL1Ai4tzMDjlYsepmSiSxRtjR8lybRLZbPZO+7T8BneCDQVLQgN/eviyV6HEaRsgZi5RuAygtFeQ7tzrU63sz8jNh0k/xwQl3n6QIyBClc33yyxV45p6RmsCNQelPFqRxDzrz909z69vH2ZjYkb346zbfEntffksoXjaawmPGGJgVB0w==
- Arc-seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=GbfoWZyX+SQm+bD68traouPvbWzkyiL9T0CPbkIqqujNvWlJAgZkc6iVOSgAb0ho22WeeOgxfuDY461HBjfJjYkN7xrmduzfIfm5eC0ky/OsDWsuXHts6zE+R4c1/ERR+QNUqNjqyUUVLVPwjafBe59+fNF+XoxFuauthSggSDnP37BkAake3Fm9ITijHeJbWbdQn9/Ea0jrzovBSgt1cHqrJeTDkmTPXo38bcPkRzwYOx/D//IGCCi8b4vSXHa6WGrCBjuklDq6lYGEiMdKsnA2WQHnTHJZns8qYpyqUgtPAsAbHzXicb7wwpT6sjsaqNWs2+QxjNi9Yda04RtdEQ==
Hi Mark,
thanks for your reply. Sorry to bother you but I tried different values for the parameter you suggested but all the time I got the same result:
I tried also using iperf2, nuttcp with no luck. Other tests like rtt went fine.
Do you have some other suggestions? Otherwise thanks for you support.
Regards From: Mark Feit <>
Danilo Berruto writes:
I’m trying to run perfsonar throughput tasks over satellite link connection but they fails all the time. Running them on a lan environment with fake delay addition using tc command gives the same results.
Are there some tweaks to let perfsonar works over an >550ms latency link?
Yes, there is. Since pScheduler requires good estimates of runtime, the iperf3 tool bases it on a RTT on what’s likely to occur on terrestrial systems. You can adjust that by adding the “link-rtt” parameter to your throughput test. PT0.6S should be sufficient for most services where the satellites are in geosynchronous orbit, but it’s worth taking some actual RTT measurements to account for additional time spent in the ground segment. Making the number larger than necessary won’t hurt other than consuming marginally more time to run the test.
--Mark
|
- [perfsonar-user] High latency error, Danilo Berruto, 03/16/2020
- <Possible follow-up(s)>
- Re: [perfsonar-user] High latency error, Mark Feit, 03/16/2020
- RE: [perfsonar-user] High latency error, Danilo Berruto, 03/17/2020
- Re: [perfsonar-user] High latency error, Mark Feit, 03/17/2020
- RE: [perfsonar-user] High latency error, Danilo Berruto, 03/17/2020
Archive powered by MHonArc 2.6.19.