You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
MRT Parsing is by far the most expensive operation in bgpdisco. Currently this is done everytime at the update interval. There should be a way to skip parsing if it can be assumed that the contents havent changed.
As there is no way to instruct bird to only dump the file if the RIB has changed, we cant rely on last-change file attribute.
Multiple Ideas:
Get checksum of the dump (possibly also against parts of the dump) and check against previous dump. We have to check if the file contains timestamps or similar frequently changing fields which occur, without having actual changes in the RIB
While checksum should be prefered if possible we could resort to comparingthe file size. This was proven in the field and should be relatively safe. This can introduce edge cases, where a route was replaced with a route with similar sized attributes and therefore filesize remains unchanged. But i dont consider this to be a big deal in such a dynamic network like the BBB, where we see usually real changes at least every few minutes.
The text was updated successfully, but these errors were encountered:
MRT Parsing is by far the most expensive operation in bgpdisco. Currently this is done everytime at the update interval. There should be a way to skip parsing if it can be assumed that the contents havent changed.
As there is no way to instruct bird to only dump the file if the RIB has changed, we cant rely on last-change file attribute.
Multiple Ideas:
The text was updated successfully, but these errors were encountered: