[ixpmanager] route server prefixes views and memory usage

[Athanasios Douitsis]

On Fri, Apr 19, 2019 at 11:37:48AM -0400, Barry O'Donovan wrote:

> Hi Athanasios,
> 
> Athanasios Douitsis wrote on 18/04/2019 04:56:
> > Thank you most kindly for your answer. However, I was merely asking
> > whether anyone else is experiencing the problem I was describing. I
> > can't imagine we are the only IX with a client announcing a great many
> > prefixes.
> 
> No, you're not. We also have it with, for example, as6939 being the worst
> case proof of concept for this.
> 
> The current recommended solution is to increase PHP's maximum memory.
> 
> If we were to keep the feature as is, the proper solution would be
> server-side pagination of some form. But this, I think, would be a waste of
> effort. How useful is this feature for the networks with sufficient prefixes
> to trigger the issue really? My feeling is not very useful and networks of
> that size would have their own tooling.
> 
> > But since you mentioned it, are you aware that the specific problem is
> > addressed somehow in the upcoming 5.x version? If affirmative, may I
> > inquire what did you do?
> 
> We now pull /only/ filtered prefixes. I.e. not potential or accepted
> prefixes. And we do this live via Birdseye from all the route servers rather
> than a cronjob-based view from a single route server.
> 
>  - Barry
> 
> (still on holidays)
> (but sitting on a bus)
> 
> 

Hello everyone,

Barry and Nishal, many thanks for your answers, that's exactly what I
was asking about. Glad to hear we're not the only ones seeing that
problem, we were beginning to wonder. What Barry hints about the upcoming
solution makes sense too.

We'll bump the PHP memory limit in the meanwhile until we have our hands
on the proper solution.

Kind regards to all and many thanks!,
-- 
Athanasios Douitsis
National Technical University of Athens NOC
e: aduitsis at noc.ntua.gr | t: +302107722409