1414codeforge/www.doublefourteen.io
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

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

Browse Source
This commit is contained in:
Lorenzo Cogotti
2021-10-20 04:08:25 +02:00
parent 929f5869aa
commit 33a995dfd2
1 changed files with 2 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
content/blog/bgpgrep-performance-facts.md
View File

@@ -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`,
to avoid any disk write overhead.
## The show's on
## Let the fun begin!
We take the data for the first benchmark from
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.
@@ -71,7 +71,7 @@ bgpdump -mv sydney/2020-12/uncompressed.mrt >/dev/null
`bgpgrep` is 11% faster than `bgpscanner`, which is good.
Since this benchmark operates mostly on MRT update dumps, let's try the same
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.
This time the benchmark is limited to `bgpgrep` and `bgpscanner`.