From: Steve Grubb <sgrubb@redhat.com>
To: linux-audit@redhat.com
Subject: Re: Benchmarking the performance impact of auditd
Date: Thu, 29 Aug 2013 16:24:34 -0400 [thread overview]
Message-ID: <3656760.dzU1SsyfMy@x2> (raw)
In-Reply-To: <CAP6dAmeoEoBPxJfD+-ckPYv0x=d5Yu67EOZ0o=tggNi9F3v8xw@mail.gmail.com>
On Thursday, August 29, 2013 12:59:33 PM zhu xiuming wrote:
> Has someone done some work related to the performance impact of enabling
> auditd on syscalls watching?
Yes, long ago.
http://people.redhat.com/sgrubb/files/lspp-perf.tar.gz
Short story is watches were undistinguishable from cache hit/misses and
syscall auditing gets more impact as more rules get added and based on how
complicated the rule is. CPU's have changed so much since I did the
benchmarking that I won't even hazard a guess as to what the performance hit
is on current hardware with current kernel.
-Steve
next prev parent reply other threads:[~2013-08-29 20:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-29 19:59 Benchmarking the performance impact of auditd zhu xiuming
2013-08-29 20:24 ` Steve Grubb [this message]
2013-08-29 21:02 ` Nathaniel Husted
2013-08-29 22:48 ` zhu xiuming
[not found] ` <CAP6dAmdSVJCDLKjRnc=BC0uq4_H_CvWQUh2KAo5_FAdtYs1TFg@mail.gmail.com>
[not found] ` <3563532.8KEs8hfWQn@x2>
2013-09-01 2:19 ` zhu xiuming
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3656760.dzU1SsyfMy@x2 \
--to=sgrubb@redhat.com \
--cc=linux-audit@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox