All of lore.kernel.org
 help / color / mirror / Atom feed
From: Simon Wunderlich <sw@simonwunderlich.de>
To: b.a.t.m.a.n@lists.open-mesh.org
Subject: Re: [B.A.T.M.A.N.] how well does batman-adv scale
Date: Wed, 26 Apr 2017 18:05:48 +0200	[thread overview]
Message-ID: <1504855.vmUtePouqW@prime> (raw)
In-Reply-To: <1493216459.18414.3.camel@openmailbox.org>

[-- Attachment #1: Type: text/plain, Size: 840 bytes --]

Hi,

"works well" depends much on  your scenario.

I've seen many well-working networks with 100-300 nodes. There are Freifunk 
community networks with over 1000 nodes running batman-adv (i.e. "standard" 
users like laptops and smartphones), but they employ a lot of filtering to 
avoid too much broadcast.

Unless you have special restrictions like minimal broadcast traffic or high 
capacity on the wireless links, memory and CPU, I would not recommend to plan 
for 10 000 nodes and beyond.

Cheers,
     Simon

On Wednesday, April 26, 2017 4:20:59 PM CEST fuumind wrote:
> Hi list!
> 
> Been lurking for almost a year on the battlemesh list and recently
> joined here as well. 
> 
> I'm curious about how well batman-adv scales. Would a network of 10 000
> nodes work well? What about 100 000 nodes or 1 000 000?
> 
> Thanks!
> fuumind


[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  parent reply	other threads:[~2017-04-26 16:05 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-26 14:20 [B.A.T.M.A.N.] how well does batman-adv scale fuumind
2017-04-26 15:10 ` jens
2017-04-26 15:53   ` dan
2017-04-26 16:06   ` fuumind
2017-04-26 16:12     ` dan
2017-04-26 16:05 ` Simon Wunderlich [this message]
2017-04-28 10:44   ` fuumind
2017-04-28 12:23     ` Simon Wunderlich
2017-04-28 14:26       ` fuumind
2017-05-02 11:35       ` Adrian Reyer

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1504855.vmUtePouqW@prime \
    --to=sw@simonwunderlich.de \
    --cc=b.a.t.m.a.n@lists.open-mesh.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.