Re: Hardware requirements for BIRD

2017-03-11 Thread Israel G. Lugo
Just to give an idea. I'm using multiple GNU/Linux routers with an Intel Atom C2758 (8-core SoC) and 8 GiB RAM to handle ~2k routes with Bird. Bird itself doesn't make a dent in CPU. These are building access routers; traffic is around 80 Mbit/s each (~ 6 kpps), with connection tracking and NAT. Us

Re: Hardware requirements for BIRD

2017-03-09 Thread Clément Guivy
Thanks everyone for your answers, that's very helpful to me :-) On 07/03/2017 19:46, Matthew Walster wrote: On 7 March 2017 at 05:57, Clément Guivy mailto:clem...@guivy.fr>>wrote: Hello, I am considering the setup of BIRD as a router to handle our internet traffic. One information I fa

Re: Hardware requirements for BIRD

2017-03-07 Thread Matthew Walster
On 7 March 2017 at 05:57, Clément Guivy wrote: > Hello, I am considering the setup of BIRD as a router to handle our > internet traffic. One information I fail to find is hardware requirements. > ​Clément, Let's just clear one thing up straight away -- BIRD is a daemon for routing protocols, no

Re: Hardware requirements for BIRD

2017-03-07 Thread Michael McConnell
Hello Clement, even the most entry level server these days will meet your requirements. Bird is very lean, a system with 2 cores and 4 gbps of ram is plenty for what you described. The only thing I would suggest is you look at Intel NIC’s like the i340 or i350 which will help a great deal if y

Re: Hardware requirements for BIRD

2017-03-07 Thread David S.
Hi, Here is my x86 router configuration: OS: FreeBSD 10.2 64bit Bird 1.6.3 CPU Intel E5-2609v2 Memory 16GB Here is top result for bird: 27 processes: 1 running, 26 sleeping CPU: 13.0% user, 0.0% nice, 1.8% system, 1.7% interrupt, 83.6% idle Mem: 504M Active, 112M Inact, 875M Wired, 518M Buf

Hardware requirements for BIRD

2017-03-07 Thread Clément Guivy
Hello, I am considering the setup of BIRD as a router to handle our internet traffic. One information I fail to find is hardware requirements. My use case is as follows : - Two transit providers, each sending a full internet view - Two peerings on an IXP (less than 100k routes e