perfsonar-user - Re: [perfsonar-user] Using perfsonar-tools
Subject: perfSONAR User Q&A and Other Discussion
List archive
- From: Mark Feit <>
- To: Gerald Vogt <>, "" <>
- Subject: Re: [perfsonar-user] Using perfsonar-tools
- Date: Fri, 9 Aug 2024 14:57:05 +0000
- Arc-authentication-results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=internet2.edu; dmarc=pass action=none header.from=internet2.edu; dkim=pass header.d=internet2.edu; arc=none
- Arc-message-signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector10001; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-AntiSpam-MessageData-ChunkCount:X-MS-Exchange-AntiSpam-MessageData-0:X-MS-Exchange-AntiSpam-MessageData-1; bh=TIhrkQOr/757Al14UVS8VeuAYM7sBvYnA8d0YQyT1gc=; b=d58uXyWNHHzBHtHfSV8yduxAX1PyYX/rtyFeZlfqZMmaNZOIRCVlFSnYZvGTLg7I2z0v564fOubaXeK91TlVk9mWC3sAzR9BvY5OMoVb+zUVkuQ30RWNfqotsu3Dd1DwnVqPDVx0StVTS0olpJhych0ksN5v8Jldqu5oc7iXcDSdEj5zjfwNLPreijQDI7gPFKWUX0APB8vlg3mBZw5oTPAUughhwKr8SPJIqvBNp3t+C+4wOacR0BqMC4ak8PPF3Rifghcw/q43xnjOkDU3chmSsblF84TUUdisIiObYNOnKUrZbnjlkfY9oDPLtSyJDO3gixvZt37Ct8TR2oRVsQ==
- Arc-seal: i=1; a=rsa-sha256; s=arcselector10001; d=microsoft.com; cv=none; b=OGfb2T224d++SgbpZFmVUdo5cvtURkoV20e+eyL3wMGHy9NtCczAweNUMLkHRbcxaOM3KWS9Mu3dchpXOdpuyjUGAZNUi7GJDii6MLNmd2lnvHq+EJ9fOmg6h7K7O0AftKyI0e7UwGGXt+tgfZnA5MPT99fSnsLbHRU4azpI0ZWHIbO4mUbiMogYxWdodpnPF2OIVwu02sBCMeDgJRHE2i1G9VZsPdPpvpv1mJNxs/iD455yGflIdXSdvnqFWsg0vr+tkNPda8so2KoHFfy+0ukzgyl6ZCyAsYtkX9auSlnaMMtYDv80NKmu+V3dYb8rOFnuR0BeZcYGoy9qplkQPg==
Gerald Vogt writes:
…
$ pscheduler task throughput --source eucgu53.euc.mpcdf.mpg.de --dest
That’s correct; there is no pScheduler server running on test.dkrz.de. One of the concepts that makes pScheduler tick is the participant, which is a system running pScheduler that’s involved in making a measurement. Many measurements don’t require more than one. For example, rtt needs one pScheduler at the source end to run ping and the other end is along for the ride by virtue of having a functioning IP stack. Conversely, the tools that we support for measuring throughput require that a process be run on each end to be the sending and receiving ends of that test. Tto run most throughput tests, both ends need pScheduler. How can I do a throughput test? Make sure pScheduler is available on both ends. I recommend installing the testpoint bundle with the security package to set up the firewall: $ curl -s https://downloads.perfsonar.net/install | sudo sh -s - --security testpoint
--Mark
|
- [perfsonar-user] Using perfsonar-tools, Gerald Vogt, 08/09/2024
- Re: [perfsonar-user] Using perfsonar-tools, Mark Feit, 08/09/2024
- Re: [perfsonar-user] Using perfsonar-tools, Gerald Vogt, 08/09/2024
- Re: [perfsonar-user] Using perfsonar-tools, Mark Feit, 08/09/2024
- Re: [perfsonar-user] Using perfsonar-tools, Gerald Vogt, 08/09/2024
- Re: [perfsonar-user] Using perfsonar-tools, Mark Feit, 08/09/2024
- Re: [perfsonar-user] Using perfsonar-tools, Gerald Vogt, 08/09/2024
- Re: [perfsonar-user] Using perfsonar-tools, Mark Feit, 08/09/2024
Archive powered by MHonArc 2.6.24.