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.

Sign up for GitHub

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

Jump to bottom

100% CPU Usage when using ModSecurity with CRS #1995

Closed
Stono opened this issue Jan 28, 2018 · 1 comment · Fixed by #1996
Closed

100% CPU Usage when using ModSecurity with CRS #1995

Stono opened this issue Jan 28, 2018 · 1 comment · Fixed by #1996

Comments

@Stono
Copy link
Contributor

Stono commented Jan 28, 2018

Hey,
ModSecurity with OWASP CRS enabled makes nginx unusable. On a 4gig/4cpu node, CPU spikes to 100% for 5-10 seconds with a single user accessing the site.

See: owasp-modsecurity/ModSecurity#1641

Suggest: switching to v3/dev/performance branch of ModSecurity until the changes are merged into Master
@Stono Stono mentioned this issue Jan 28, 2018
Merged
@Stono
Copy link
Contributor Author

Stono commented Jan 28, 2018

Stuck in a pull request to use the performance improvements in relation to this issue, I appreciate it would be nicer to wait until those changes are in master however modsecurity with crs is currently unusable for me (and I presume others!?).

@Stono Stono mentioned this issue Jan 28, 2018
Closed
@CRS-migration-bot CRS-migration-bot mentioned this issue May 13, 2020
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Use v3/dev/performance of ModSecurity because of performance
1 participant
@Stono