[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Proving Gig Speed

Subject: Proving Gig Speed
From: mark.tinka at seacom.mu (Mark Tinka)
Date: Tue, 17 Jul 2018 14:11:35 +0200
In-reply-to: <CAE-M_OBQTxjf0RZODST_jS67Ldy5OoYbgactqqw_gKWPTAaawg@mail.gmail.com>
References: <DM6PR17MB207641B5B0FDAAD24EEABA36CA5D0@DM6PR17MB2076.namprd17.prod.outlook.com> <CAHk8tam7epDSZtk76174Zx8kSFeX=-W8q_P4-8Qpw=+8cP9aEw@mail.gmail.com> <DM6PR17MB207636E3CA0358DFD57E054ACA5D0@DM6PR17MB2076.namprd17.prod.outlook.com> <MW2PR12MB2380D20D18E5C03F4665743EA05D0@MW2PR12MB2380.namprd12.prod.outlook.com> <[email protected]> <CAE-M_OBQTxjf0RZODST_jS67Ldy5OoYbgactqqw_gKWPTAaawg@mail.gmail.com>

On 17/Jul/18 14:07, K. Scott Helms wrote:

>
> That's absolutely true, but I don't see any real alternatives in some
> cases.Â  I've actually built automated testing into some of the CPE
> we've deployed and that works pretty well for some models but other
> devices don't seem to be able to fill a ~500 mbps link.

So what are you going to do when 10Gbps FTTH into the home becomes the norm?

Perhaps laptops and servers of the time won't even see this as a
rounding error :-\...

Mark.

Follow-Ups:
- Proving Gig Speed
  - From: nanog at ics-il.net (Mike Hammett)
- Proving Gig Speed
  - From: kscott.helms at gmail.com (K. Scott Helms)

References:
- Proving Gig Speed
  - From: CGross at ninestarconnect.com (Chris Gross)
- Proving Gig Speed
  - From: merculiani at gmail.com (Matt Erculiani)
- Proving Gig Speed
  - From: CGross at ninestarconnect.com (Chris Gross)
- Proving Gig Speed
  - From: carlos at race.com (Carlos Alcantar)
- Proving Gig Speed
  - From: mark.tinka at seacom.mu (Mark Tinka)
- Proving Gig Speed
  - From: kscott.helms at gmail.com (K. Scott Helms)

Prev by Date: Proving Gig Speed
Next by Date: Proving Gig Speed
Previous by thread: Proving Gig Speed
Next by thread: Proving Gig Speed
Index(es):
- Date
- Thread