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
Currently, setting up a new source triggers a call to net.InterfaceByName(<name>), which in turn calls a stack of methods to retrieve the current list of interfaces, leading to quite expensive syscall invocations. While being ok(ish) for single instances and / or few static interfaces, in situations where a lot of interfaces and / or a large number of instabilities (causing repeated up / down and hence re-initialization actions) this can cause significant overhead in total.
DoD
Assess options to minimize overhead (why is a deep call required to perform this lookup?)
Remove complex lookup call upon interface initialization
At least provide an option to provide a (reusable) net.Interfaces list upon initialization to reduce overhead when bulking
The text was updated successfully, but these errors were encountered:
Currently, setting up a new source triggers a call to
net.InterfaceByName(<name>)
, which in turn calls a stack of methods to retrieve the current list of interfaces, leading to quite expensivesyscall
invocations. While being ok(ish) for single instances and / or few static interfaces, in situations where a lot of interfaces and / or a large number of instabilities (causing repeated up / down and hence re-initialization actions) this can cause significant overhead in total.DoD
At least provide an option to provide a (reusable)net.Interfaces
list upon initialization to reduce overhead when bulkingThe text was updated successfully, but these errors were encountered: