Skip to Content.
Sympa Menu

perfsonar-user - Re: [perfsonar-user] OWAMP on a Pi 3

Subject: perfSONAR User Q&A and Other Discussion

List archive

Re: [perfsonar-user] OWAMP on a Pi 3


Chronological Thread 
  • From: "Dale W. Carder" <>
  • To: Steven Wallace <>
  • Cc: Ian Bobbitt <>,
  • Subject: Re: [perfsonar-user] OWAMP on a Pi 3
  • Date: Fri, 9 Sep 2016 00:06:11 -0500
  • Ironport-phdr: 9a23:zTziQBEU7fBLhtuKZCnh351GYnF86YWxBRYc798ds5kLTJ76rsywAkXT6L1XgUPTWs2DsrQf1LqQ7vurADFIyK3CmU5BWaQEbwUCh8QSkl5oK+++Imq/EsTXaTcnFt9JTl5v8iLzG0FUHMHjew+a+SXqvnY6Uy/yPgttJ+nzBpWaz4Huj7jzqNXvZFBzmDejbLU6ExyyqQzau4FCmpB9AqcsjBbFvy0bVf5RwDYiCVuXkl7DoI+b9YRv/j4a86Yt6MVJS6n3ZYw1VvpeAShwYDN939HiqRSWFVjH3XAbSGhD10MQWwU=
  • Ironport-phdr: 9a23:DQvm8RffiOo885DatWT16KR/lGMj4u6mDksu8pMizoh2WeGdxc6yYR7h7PlgxGXEQZ/co6odzbGH6ua+AidRu97B6ClEK80UEUddyI0/pE8JOIa9E0r1LfrnPWQRPf9pcxtbxUy9KlVfA83kZlff8TWY5D8WHQjjZ0IufrymUrDbg8n/7e2u4ZqbO1wO32vkJ+0pZ0Ts5UWJ749N0NMkcv5wgjLy4VJwM9xMwm1pIV/B1z3d3eyXuKBZziJLpvg6/NRBW6ipN44xTLhfESh0ezttvJ6jnVD5QACO/noRVHkN2loNWlCdrUKyYpCkiTf3qOd7kBaTOcn/Rr18DS+58I9qVVnlhDpRZBAj92SCwOB5iK8Tn1TpjBVlz4POKsnBOOV1d7nRcMkySHEHWMtNAX8SSrigZpcCWrJSdd1TqJPw8h5X9UOz


A beaglebone black with something like a LEA-6T would be interesting to try.


Dale

Thus spake Steven Wallace
()
on Thu, Sep 08, 2016 at 04:48:45PM -0400:
> thanks Ian.
>
> Any comments about the beaglebone? Anyone using a DS3231-based clock?
>
> ssw
>
>
> > On Sep 8, 2016, at 2:27 PM, Ian Bobbitt
> > <>
> > wrote:
> >
> > On 9/8/16 11:51 AM, Steven Wallace wrote:
> >> I realize that underpowered ARM-based platforms aren't support, but I
> >> wonder if anyone has experience running OWAMP on a Raspberry Pi 3 or
> >> similar.
> >>
> >>
> >> if so, can you share some details such as OS, clock source, experience,
> >> etc.
> >>
> >> thanks,
> >>
> >> steve wallace
> >>
> >
> > Steve,
> >
> > A Raspberry Pi 3 should work fine for OWAMP if you only want to show
> > loss, but probably not appropriate to show jitter.
> > The Pi 3 has two means of network connectivity.
> >
> > 1) On-board WiFi. Pretty well known to have poor jitter performance,
> > especially under load or in a noisy environment. It
> > only supports 2.4GHz, which is pretty crowded everywhere. Loss is also
> > pretty much a given on WiFi.
> >
> > 2) On-board USB Ethernet. USB also has poor jitter performance. This is
> > compounded by it being shared (via on-chip hub)
> > with the external USB ports.
> >
> > Ian Bobbitt
>



Archive powered by MHonArc 2.6.19.

Top of Page