debian stretch, bird v 1.6.3-2 is rock solid

FWIW i saw zero leaks or issues on debian wheezy, jessie, devuan jessie either.

on multiple rrs taking several million routes I am at:

birdc
BIRD 1.6.3 ready.
bird> show mem
BIRD memory usage
Routing tables:    126 MB
Route attributes:   93 MB
ROA tables:        112  B
Protocols:         823 kB
Total:             219 MB

alpine linux also works very well, no issues taking multiple full tables on core/edge as well:

(host: core1)  (user: root)  (time= 11:23:53)
 > ~ # birdc
BIRD 1.6.0 ready.
bird> show mem
BIRD memory usage
Routing tables:    182 MB
Route attributes:  156 MB
ROA tables:        192  B
Protocols:         686 kB
Total:             339 MB
bird>





On Fri, 13 Apr 2018, Willy Goiffon wrote:

Hello,

I installed different version of bird on Ubuntu 16.04 (namely, 1.5.0, 1.6.3, 1.6.4).
After leaving the daemon running for ~1 hour, the memory used by the
host is over 8Gib. However, when running `birdc show memory`, I get
the following:

       BIRD memory usage
       Routing tables:     21 kB
       Route attributes:   11 kB
       ROA tables:        192  B
       Protocols:          22 kB
       Total:             102 kB

My config is pretty basic (edited, see attached) as we have 2 BGP
protocols using 2 ASN (one public, one private), each exporting the
routes learnt from the other.

The leak seems to be related to the traffic going through the server,
as the memory of the host remains still when there is no traffic
going on. It is triggered by bird though, because I don't have the
leak when the routes are configured statically and bird is shut down.

The weird thing about this is that the memory is not used by the bird
process itself. It's shown as used memory by the host, but no process
is actually using this memory.
I know that it's leaking because of bird though because it's the only
process installed and running on this host.

Has anyone ever encountered such a behavior, or can see an issue in
my configuration?

Thanks in advance for your help
--
Willy

Reply via email to