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

zeek handle 230m/s of traffic, each work memory keeps rising #390

Closed
shuaidonga opened this issue May 30, 2019 · 4 comments

Comments

Projects
None yet
3 participants
@shuaidonga
Copy link

commented May 30, 2019

Bro is handling 230m/s of traffic, and the memory growth of each work over time causes system memory to run out.
image
Bro with PF_RING is configured as follows
image

Centos machine configuration is as follows 40 core cpu, 64G memory。

Bro resource occupancy
image.

Is there an optimized way?

@shuaidonga

This comment has been minimized.

Copy link
Author

commented May 30, 2019

Increase cpu to 30, then logger takes up memory growth.
image

@schenksj

This comment has been minimized.

Copy link

commented Jun 1, 2019

@aeppert is this the issue you resolved locally?

@shuaidonga

This comment has been minimized.

Copy link
Author

commented Jun 3, 2019

What can I do to optimize?
@schenksj @aeppert @jsiwek

@rsmmr

This comment has been minimized.

Copy link
Member

commented Jun 12, 2019

This looks better suited for discussion on the mailing list.

@rsmmr rsmmr closed this Jun 12, 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.