What you're saying isn't too clear by "churn through that job". Do you mean when your upstream routing sessions are coming up, it takes 15 minutes to process all the routes? Do you mean commit?
Scott On Thu, Sep 8, 2011 at 7:41 AM, Mike Williams <mike.willi...@comodo.com>wrote: > Hi all, > > Recently a discussion touched on the routing engine speed of the MX series, > but there wasn't much like a "real world" comparison. > So my question is, how slow is the RE on an MX80 compared to it's bigger > brethren? > > I ask because we find the MX80 slow, really slow. > As we've got 2 distinctly different traffic types, and 2 distinctly > different > upstreams (1Gbps and 10Gbps), we're using a rib group and policy to > populate > 2 additional ribs with different local preferences applied to the learnt > routes. Filters direct packets to the right table. > It'll take the RE a good 10-15 minutes to churn through that job, and > that's a > bit annoying when you make a small change to a unrelated policy! > Now, is that us being stupid, or the RE being slow? I know what I'd like to > hear :) > > > Cheers > > -- > Mike Williams > _______________________________________________ > juniper-nsp mailing list juniper-nsp@puck.nether.net > https://puck.nether.net/mailman/listinfo/juniper-nsp > _______________________________________________ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
