From: "Jonas Mårtensson" <martensson.jonas@gmail.com>
To: Mikael Abrahamsson <swmike@swm.pp.se>
Cc: Jan Ceuleers <jan.ceuleers@gmail.com>,
bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] 22 seconds til bloat on gfiber?
Date: Thu, 27 Oct 2016 16:32:55 +0200 [thread overview]
Message-ID: <CAM9iV=+TkjrM5X6GnYKVRVNOv0F3OL+WbqxD6QbVG6gECC-Mqg@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1610261733530.12036@uplift.swm.pp.se>
[-- Attachment #1: Type: text/plain, Size: 1378 bytes --]
On Wed, Oct 26, 2016 at 5:36 PM, Mikael Abrahamsson <swmike@swm.pp.se>
wrote:
> On Wed, 26 Oct 2016, Jan Ceuleers wrote:
>
> What I mean is that the OLT optics become very expensive if you need to
>> support as many lambdas as you have customers. You'd furthermore need an
>> OLT port for much fewer customers (e.g. 1 port per 64 or 128 customers)
>> than the thousands you can support on a (shared) GPON port on a single
>> lambda.
>>
>
> That only works if your customers don't use their Internet access very
> much. If they do, you're in trouble and have to rebuild.
>
Yes, and the question then becomes: How much is "very much"? This can of
course be analyzed mathematically, which e.g. Google have done here:
http://research.google.com/pubs/pub44935.html
>
> In my market, we're now in the access speeds where 100/10 is on the lower
> end of access, and it's not uncommon for people to have 250, 500 or 1000
> downstream. If they then actually start using their bw then you'd have to
> rebuild to either go higher speed for some CPE (complicated and expensive),
> or rebuild to have smaller splitter domains.
>
The standard answer from PON proponents (I'm not one) is to upgrade
equipment, from GPON to XG-PON or NG-PON2. But upgrading hardware as
bandwidth demand increases is necessary whatever the technology - what's
important is the scalability of the solution.
[-- Attachment #2: Type: text/html, Size: 2188 bytes --]
next prev parent reply other threads:[~2016-10-27 14:32 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-22 21:56 Dave Taht
2016-10-22 23:52 ` Jonathan Morton
2016-10-23 1:33 ` jb
2016-10-23 1:45 ` Dave Taht
2016-10-23 1:47 ` Dave Taht
2016-10-23 2:27 ` jb
[not found] ` <CAJq5cE3DsV9v6ATVeq+vF_kVFjKy+8Qjwe-P01ZZbyKZB9HC6w@mail.gmail.com>
2016-10-23 8:29 ` Jonathan Morton
2016-10-23 9:23 ` jb
2016-10-23 16:14 ` Klatsky, Carl
2016-10-24 0:46 ` jb
2016-10-24 13:13 ` Klatsky, Carl
2016-10-24 16:11 ` Noah Causin
2016-10-24 20:27 ` Klatsky, Carl
2016-10-23 2:30 ` Benjamin Cronce
2016-10-25 7:10 ` Jonas Mårtensson
2016-10-23 5:50 ` Mikael Abrahamsson
2016-10-24 16:57 ` Jonas Mårtensson
2016-10-24 22:10 ` Benjamin Cronce
2016-10-25 0:09 ` jb
2016-10-25 12:01 ` Benjamin Cronce
2016-10-25 13:11 ` Klatsky, Carl
2016-10-25 21:20 ` jb
2016-10-26 0:02 ` Klatsky, Carl
2016-10-25 15:59 ` Jan Ceuleers
2016-10-26 1:05 ` Benjamin Cronce
2016-10-26 14:49 ` Jan Ceuleers
2016-10-26 15:36 ` Mikael Abrahamsson
2016-10-27 14:32 ` Jonas Mårtensson [this message]
2016-10-27 16:56 ` Dave Taht
2016-10-27 17:56 ` [Bloat] Sidebar on s-curves David Collier-Brown
2016-10-27 19:30 ` [Bloat] 22 seconds til bloat on gfiber? David Lang
2016-10-27 19:41 ` Dave Taht
2016-10-27 19:48 ` Aaron Wood
2016-10-28 15:51 ` Jan Ceuleers
2016-10-28 15:55 ` Klatsky, Carl
2016-10-27 19:45 ` Aaron Wood
2016-10-27 20:17 ` Mikael Abrahamsson
2016-12-07 5:40 ` Jonathan Morton
2016-12-07 7:05 ` Mikael Abrahamsson
[not found] <mailman.313.1477591111.3555.bloat@lists.bufferbloat.net>
2016-10-27 19:27 ` Jonathan Foulkes
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://lists.bufferbloat.net/postorius/lists/bloat.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAM9iV=+TkjrM5X6GnYKVRVNOv0F3OL+WbqxD6QbVG6gECC-Mqg@mail.gmail.com' \
--to=martensson.jonas@gmail.com \
--cc=bloat@lists.bufferbloat.net \
--cc=jan.ceuleers@gmail.com \
--cc=swmike@swm.pp.se \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox