owasp-modsecurity / owasp-modsecurity/ModSecurity
Bad performance when used with threaded mpms and a libapr compiled with "--enable-allocator-uses-mmap" option
Open
@victorhora is already working on this.
Since Feb 2, 2019.
Platform - Apache
- Dominant language
- C++
- Stars
- 9.8k
- Forks
- 1.8k
- Avg merge
- 2h 46m
- Merged PRs (30d)
- 1
Description
Originally reported by: Nelson Elhage and Stefan Fritsch.
It seems that ModSecurity is having bad performance whenever used with threaded mpms and a libapr compiled with "--enable-allocator-uses-mmap" option.
According to Stefan that option is used on apr's Debian package for over 3 years.
It is somehow related to the way that ModSecurity is individually handling every connection, by created a new memory allocator.
Relevant piece of code:
Original report:
- https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=758068
Option "--enable-allocator-uses-mmap" was added on libapr by Stefan as of 1.4.3, ChangeLog: - http://svn.apache.org/viewvc/apr/apr/branches/1.4.x/CHANGES?view=markup
Mail sent to ModSecurity devs mailing list: - http://sourceforge.net/p/mod-security/mailman/message/32723547/
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.