Re: BIRD memory usage

I *think* I have answered my own question. The patch in the email doesn't include the switch to xmalloc that was originally in the krt-export-filtr-fix branch as well. I can see from `git blame` that it's in the previous commit, bc00f058154bb4a630d24d64a55b5f181d235c63 [ Filter: Prefer

Re: BIRD memory usage

Ok - great. Should this patch apply to the 1.6 released version ok ? I was tracking from the krt-export-filtr-fix before, that that is now gone :) Cheers, Just On 19 September 2016 at 10:13, Ondrej Zajicek wrote: > On Mon, Sep 19, 2016 at 09:46:03AM +0100, Justin

Re: BIRD memory usage

; >>>>> } >>>>> >>>>> -static int rte_update_nest_cnt; /* Nesting counter to allow >>>>> recursive >>>>> updates */ >>>>> - >>>>> -static inline void >>>>> -rte_update_lock(void) &g

Re: BIRD memory usage

gt; - rte_update_nest_cnt++; >>>> -} >>>> - >>>> -static inline void >>>> -rte_update_unlock(void) >>>> -{ >>>> - if (!--rte_update_nest_cnt) >>>> -lp_flush(rte_update_pool); >>>> -} &

Re: BIRD memory usage

e, which then seems to grow indefinitely in distinct steps, separated by a period of a few hours. In production, this consumes most of the 32G of memory until the kernel oom-killer to intervenes. Production: BIRD 1.5.0 ready. bird> show memory BIRD memory usage Routing tables: 1405 MB Route

Re: BIRD memory usage

ready. 2391 of 2391 routes for 1201 networks # birdc show mem BIRD 1.6.0 ready. BIRD memory usage Routing tables:246 kB Route attributes: 88 kB ROA tables:192 B Protocols: 45 kB Total: 416 kB # pmap $(pgrep "bird$") |grep total total

Re: BIRD memory usage

Hi Ondrej, Yes - it's a version from git with BGP multipath support: v1.5.0-19-g8d9eef1. Cheers, Just On 6 September 2016 at 17:05, Ondrej Zajicek wrote: > On Mon, Sep 05, 2016 at 03:21:40PM +0100, Justin Cattle wrote: > > Hi, > > > > > > A colleague of mine

Re: BIRD memory usage

; >> In production, this consumes most of the 32G of memory until the >> kernel oom-killer to intervenes. >> >> Production: >>> >>> BIRD 1.5.0 ready. >>> >>> bird> show memory >>> >>> BIRD memory usage >>> >

Re: BIRD memory usage

ormal" memory usage, which then seems to grow indefinitely in distinct steps, separated by a period of a few hours. In production, this consumes most of the 32G of memory until the kernel oom-killer to intervenes. Production: BIRD 1.5.0 ready. bird> show memory BIRD memory usage Routing t

Re: BIRD memory usage

On Mon, Sep 21, 2015 at 10:10:08AM +0200, Alexander Frolkin wrote: > Hi Ondrej, > > > > Is there something we can do to reduce the memory usage? Or could this > > > be a memory leak bug? > > This is definitely a memory leak, probably related to path merging. You > > are using current code from

Re: BIRD memory usage

Hi Ondrej, > > Is there something we can do to reduce the memory usage? Or could this > > be a memory leak bug? > This is definitely a memory leak, probably related to path merging. You > are using current code from git or patched 1.5.0? I will try to reproduce > it. Thanks. We are using a