issue with PEVAL output
nick at inex.ie
Wed Sep 14 10:40:34 UTC 2016
Temoor Khan wrote:
> I have tried AS-RUNNET & AS-Hurricane. I wonder if it is somehow related
> to the compute power of the machine I am running these commands on.
Good old AS-HURRICANE: currently 970,000 prefix entries and growing.
The problem is not related to compute power. peval chews a bit of
memory but no CPU. whois.radb.net occasionally drops connections, so it
might have been a temporary problem.
If it's a persistent problem, maybe it's related to firewall settings?
You should really use bgpq3 instead of peval. bgpq3 uses query
pipelining and is worth retooling around. E.g.
> % time bgpq3 as-runnet > /dev/null
> 0.146u 0.000s 0:02.77 5.0% 77+841k 0+0io 0pf+0w
> % time peval as-runnet > /dev/null
> 4.198u 0.073s 5:39.47 1.2% 738+437k 0+0io 0pf+0w
I.e. bgpq3 completes the query 122 times faster than peval. It also
supports json output, which is easier to parse than free-text.
More information about the irrtoolset