Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Address CAF spinlock problem #380

Open
jsiwek opened this issue May 24, 2019 · 0 comments

Comments

@jsiwek
Copy link
Member

commented May 24, 2019

Using the work-stealing CAF scheduler, we've observed the spinlock used by its double-ended-queue being a cpu hog. Unclear exactly why, but introducing a 1 microsecond sleep to the spinlock resolved the issue. Either need to coordinate to get that improved in upstream CAF and patched for Zeek 3.0 or else try switching to the work-sharing CAF scheduler, which doesn't use a spinlock (the work-stealing I don't think best fits our default use-case anyway: we don't need a high level of concurrency or particularly low latency).

@jsiwek jsiwek added this to the 3.0.0 milestone May 24, 2019

@jsiwek jsiwek self-assigned this May 24, 2019

@jsiwek jsiwek added this to Unassigned / Todo in Release 3.0.0 via automation May 24, 2019

@jsiwek jsiwek moved this from Unassigned / Todo to Assigned / In Progress in Release 3.0.0 May 29, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.