mirror of
https://github.com/zeek/zeek.git
synced 2025-10-02 14:48:21 +00:00
![]() It may generally be better for our default use-case, as workers may save a few percent cpu utilization as this policy does not have to use any polling like the stealing policy does. This also helps avoid a potential issue with the implementation of spinlocks used in the work-stealing policy in current CAF versions, where there's some conditions where lock contention causes a thread to spin for long periods without relinquishing the cpu to others. |
||
---|---|---|
.. | ||
__load__.zeek | ||
log.zeek | ||
main.zeek | ||
README | ||
store.zeek |
The Broker communication framework facilitates connecting to remote Zeek instances to share state and transfer events.