Skip to Content.
Sympa Menu

perfsonar-user - Re: [perfsonar-user] Throughput test - perfsonar

Subject: perfSONAR User Q&A and Other Discussion

List archive

Re: [perfsonar-user] Throughput test - perfsonar


Chronological Thread 
  • From: Szymon Trocha <>
  • To:
  • Cc:
  • Subject: Re: [perfsonar-user] Throughput test - perfsonar
  • Date: Fri, 1 Feb 2019 13:53:25 +0100
  • Ironport-phdr: 9a23:yX6fFRe/TM/1pSsslEDGWjQQlGMj4u6mDksu8pMizoh2WeGdxcW6Yx7h7PlgxGXEQZ/co6odzbaO4+a4ASQp2tWoiDg6aptCVhsI2409vjcLJ4q7M3D9N+PgdCcgHc5PBxdP9nC/NlVJSo6lPwWB6nK94iQPFRrhKAF7Ovr6GpLIj8Swyuu+54Dfbx9HiTahYr5+Ngm6oRnMvcQKnIVuLbo8xAHUqXVSYeRWwm1oJVOXnxni48q74YBu/SdNtf8/7sBMSar1cbg2QrxeFzQmLns65Nb3uhnZTAuA/WUTX2MLmRdVGQfF7RX6XpDssivms+d2xSeXMdHqQb0yRD+v6bpgRh31hycdLzM37X/ZisJwgqJcoxyvqRJwzIHWb46JL/d+ZL/RcMkASGZdUMtcVSpMCZ68YYsVCOoBOP5VoZT8ploOqBu+Ag+sD/7xxD9SgX/5wa063P48GgzBxwwhHtIPsHHTrNXzLqsSTfq1zK7UwjXDdfxbwjL955LOchw7ufGMWrNxcczLxkkpDQ/FllGQpJXjMjiI2OoNtG2b4PBhVeKpk2MrtR19ria1ysojioTFnJ8Zx1PH+Cljwos4JMW0SFZgYd6iDJRcrTmaN49uTsw+XmFouCU6xqcYtpGmYSgG0JcnxwTBZPyAdYiH/A7jWPyXIThmmHJpYKq/iAqp8Ui70OH8Ts203VBXpSRGitnBrm4B2wDP5sSaT/Zw/Vut1DWK2g3W9+1JI045mK/GJ5I82rI8i5oevVjZEiPomEj7g7Waelgm9+Wm8ejrf6jqq5mBPIFukA7+KL4hmsmnDOQ4LAcOW2+b9Pyn27L95035XbFKgecsnqncqp/aI94Xpra+Aw5U1IYs8RC/Ay2+0NQchXUHLVRFdwybj4XxJV3CPOz0Aeq6jlmvjDtmxPXLM7j8DpjPIHXOlartcatl505Z0gUzzNRf55xOCrEGJfL+QlTxtd3YDx88NAy0xfzrCMln1oMZRW2PArWWPbjXsVCS4OIjOfGMZIgUuTb7Mfcl4eTijWc9mVMFZ6mmwYMXaGykHvRhO0iZeWTjgs0PEWcRuQo+SvbliEebXT5OfHa9Qbg86yo/CIKnFofDWputjKaA3Ce9Ap1ZeHpGClaSHnf0aYmIQekDZz+PIpwprjtRT6moTach1hC+8gn31+lJNO3RrxYKpJfk0pBJ/erYlRh6oSdmHsGa1SeRVWZ/nmogQjYwmrh4s0p0zBGb1f4r0LRjCdVP6qYRAU8BPpnGwrkiBg==
  • Organization: PCSS

W dniu 01.02.2019 o 05:55, Ryan Ng pisze:

TO Whom It May Concern,

 

It is Ryan from Hong Kong Internet eXchange. I’m writing to regarding the test result of Throughput test on perfSONAR.

 

Actually our perfsonar server (https://202.45.188.76) has been set up. When we try to schedule the “throughput test” with someone and the testing results (throughput, latency and loss) should be shown on the front page.

 

However, only throughput result can be shown and latency & loss result are n/a. Could you give me some advice?

 

 

 

Hi Ryan,

There may be a couple of reasons for that.

I see other tests from your host (like to tps1-1gbps.itsc.cuhk.edu.hk) are working correctly. I can also easily run latency test to this host:

$ pscheduler task latency --dest ps.daeg.kreonet.net
Submitting task...
Task URL:
https://localhost/pscheduler/tasks/a30bf151-9af0-4a9d-bf4e-6928ddec0c09
Running with tool 'owping'
Fetching first run...

Next scheduled run:
https://localhost/pscheduler/tasks/a30bf151-9af0-4a9d-bf4e-6928ddec0c09/runs/1d0145ea-b9a8-4922-bcdf-386c64070d7f
Starts 2019-02-01T12:44:12Z (~7 seconds)
Ends   2019-02-01T12:44:33Z (~20 seconds)
Waiting for result...


Packet Statistics
-----------------
Packets Sent ......... 100 packets
Packets Received ..... 100 packets
Packets Lost ......... 0 packets
Packets Duplicated ... 0 packets
Packets Reordered .... 0 packets

One-way Latency Statistics
--------------------------
Delay Median ......... 130.76 ms
Delay Minimum ........ 130.63 ms
Delay Maximum ........ 130.98 ms
Delay Mean ........... 130.78 ms
Delay Mode ........... 130.75 ms
Delay 25th Percentile ... 130.73 ms
Delay 75th Percentile ... 130.84 ms
Delay 95th Percentile ... 130.90 ms
Max Clock Error ...... 6.4 ms
Common Jitter Measurements:
    P95 - P50 ........ 0.14 ms
    P75 - P25 ........ 0.12 ms
    Variance ......... 0.01 ms
    Std Deviation .... 0.07 ms
Histogram:
    130.63 ms: 1 packets
    130.64 ms: 1 packets
    130.65 ms: 1 packets
    130.66 ms: 3 packets
    130.67 ms: 1 packets
    130.68 ms: 1 packets
    130.69 ms: 1 packets
    130.70 ms: 4 packets
    130.71 ms: 4 packets
    130.72 ms: 4 packets
    130.73 ms: 8 packets
    130.74 ms: 9 packets
    130.75 ms: 10 packets
    130.76 ms: 6 packets
    130.78 ms: 6 packets
    130.79 ms: 2 packets
    130.80 ms: 5 packets
    130.81 ms: 2 packets
    130.82 ms: 5 packets
    130.83 ms: 1 packets
    130.85 ms: 5 packets
    130.86 ms: 5 packets
    130.87 ms: 4 packets
    130.88 ms: 2 packets
    130.89 ms: 2 packets
    130.90 ms: 3 packets
    130.91 ms: 2 packets
    130.98 ms: 2 packets

TTL Statistics
--------------
TTL Median ........... 244.00
TTL Minimum .......... 244.00
TTL Maximum .......... 244.00
TTL Mean ............. 244.00
TTL Mode ............. 244.00
TTL 25th Percentile ... 244.00
TTL 75th Percentile ... 244.00
TTL 95th Percentile ... 244.00
Histogram:
    244: 100 packets

No further runs scheduled.
$

Try running same test from CLI: pscheduler task latency --dest ps.daeg.kreonet.net to see if it works.

I guess you setup a One-way latency test to this host in addition to throughput test. If yes I would say look at the network path between your host and the target one - there may be ACLs in between. I also noticed the kreonet host has policy "R&E Only" which may have impact on your tests, depending what the local administrator really mean.

It's also worth looking at /var/log/pscheduler/pscheduler.log for some obvious errors.

Best regards,

--
Szymon Trocha
Poznań Supercomputing & Networking Center
General NOC phone +48 61-858-2015 | noc.pcss.pl
Personal desk phone +48 61-858-2022 Wysłaliśmy do Ciebie ten e-mail w odpowiedzi na Twoje zapytanie lub w związku z oferowaną usługą. Przesłanie korespondencji do Centrum Zarządzania PCSS lub zgłoszenie telefoniczne jest równoznaczne z wyrażeniem zgody na przetwarzanie danych osobowych przez Instytut Chemii Bioorganicznej Polskiej Akademii Nauk w Poznaniu adres: ul. Z. Noskowskiego 12/14, 61-704 Poznań. Szczegółowe informacje znajdują się w naszej Polityce prywatności. | This message has been sent as a part of communication with PSNC NOC or your service request sent to us. For more information read our Privacy Policy.

PNG image




Archive powered by MHonArc 2.6.19.

Top of Page