[blog/bgpgrep-performance-facts] Few fixes and improvements

master
Lorenzo Cogotti 3 years ago
parent 929f5869aa
commit 33a995dfd2

@ -49,7 +49,7 @@ after one warmup round. MRT data is decompressed upfront, to avoid accounting fo
decompression overhead, the output is sent directly to `/dev/null`, decompression overhead, the output is sent directly to `/dev/null`,
to avoid any disk write overhead. to avoid any disk write overhead.
## The show's on ## Let the fun begin!
We take the data for the first benchmark from We take the data for the first benchmark from
RouteViews' [Sydney Route Collector](http://archive.routeviews.org/route-views.sydney/bgpdata), RouteViews' [Sydney Route Collector](http://archive.routeviews.org/route-views.sydney/bgpdata),
and pull the very first RIB of December 2020, along with any subsequent updates from the same month. and pull the very first RIB of December 2020, along with any subsequent updates from the same month.
@ -71,7 +71,7 @@ bgpdump -mv sydney/2020-12/uncompressed.mrt >/dev/null
`bgpgrep` is 11% faster than `bgpscanner`, which is good. `bgpgrep` is 11% faster than `bgpscanner`, which is good.
Since this benchmark operates mostly on MRT update dumps, let's try the same Since this benchmark operates mostly on MRT update dumps, let's try the same
on a different dataset, mostly made of RIBs. on a different dataset, mostly made of RIBs.
We pull nine RIBs from RIPE RIS NCC [RRC00 Route Collector]](https://data.ris.ripe.net/rrc00/2019.12/), We pull nine RIBs from RIPE RIS NCC [RRC00 Route Collector](https://data.ris.ripe.net/rrc00/2019.12/),
and obtain 25.7GB worth of uncompressed MRT data. and obtain 25.7GB worth of uncompressed MRT data.
This time the benchmark is limited to `bgpgrep` and `bgpscanner`. This time the benchmark is limited to `bgpgrep` and `bgpscanner`.

Loading…
Cancel
Save