From: Con Kolivas <kernel@kolivas.org>
To: linux kernel mailing list <linux-kernel@vger.kernel.org>
Cc: Andrew Morton <akpm@digeo.com>, zwane@holomorphy.com
Subject: tbench as a load - DDOS attack?
Date: Sun, 16 Feb 2003 10:07:25 +1100 [thread overview]
Message-ID: <200302161007.25149.kernel@kolivas.org> (raw)
Zwane M suggested using tbench as a load to test one of his recent patches and
gave me the idea to try using tbench_load in contest. Here are the first set
of results I got while running tbench 4 continuously (uniprocessor machine):
tbench_load:
Kernel [runs] Time CPU%
test2420 1 180 38.9
test2561 1 970 7.7
This is a massive difference. Sure tbench was giving better numbers on 2.5.61
but it caused a massive slowdown. I wondered whether this translates into
being more susceptible to ping floods or DDOS attacks? You should have seen
tbench 16 - 3546 seconds!
comments?
Con
next reply other threads:[~2003-02-15 22:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-15 23:07 Con Kolivas [this message]
2003-02-15 23:24 ` tbench as a load - DDOS attack? Zwane Mwaikambo
2003-02-16 0:48 ` Con Kolivas
2003-02-16 9:30 ` Andrew Morton
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=200302161007.25149.kernel@kolivas.org \
--to=kernel@kolivas.org \
--cc=akpm@digeo.com \
--cc=linux-kernel@vger.kernel.org \
--cc=zwane@holomorphy.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