From: "Adolf Belka (ipfire-dev)" <adolf.belka@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: Fireperf: first tests an results
Date: Fri, 12 Feb 2021 13:30:48 +0100 [thread overview]
Message-ID: <e0545e4d-cce7-4869-c559-9efccfb1ee09@ipfire.org> (raw)
In-Reply-To: <ae6acab7fc942043623641975f573525@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 2102 bytes --]
Hi all,
I tried to also test this out on my system.
As I am not familiar with what all the command options do I just followed Daniels commands.
server: IPFire 2.25 - Core Update 153; Intel Celeron CPU J1900 @ 1.99GHz x4; I211 Gigabit Network Connection
client: Arch Linux; Intel Core i5-8400 CPU @ 2.80GHz 6 core; 1GBit nic
Server:
fireperf -s -P 10000 -p 63000:630010
Client:
fireperf -c <IP address> -P 1 -x -p 63000:63010 where <IP address> was replaced with the IP address of my IPFire Green connection.
I started the server fireperf and there was the table updating regularly.
I started the client and got "Could not open socket: Address family not supported by protocol" scrolling up the screen.
I looked in the log (journalctl) but there were no messages at all related to fireperf just the command being run.
Any thoughts on what I am missing to have setup or installed?
Regards,
Adolf.
On 09/02/2021 13:53, daniel.weismueller(a)ipfire.org wrote:
>
>
> Hi guys,
>
> today I installed fireperf on my testing IPFire and my Ubuntu PC.
>
> server: IPFire Core 154; Intel i7 4790; Intel 82571EB/GB 1GBit Nic
> Client: Ubuntu 20.4; Intel i7 9700; Intel i219-V 1GBit Nic
>
> Michael and I agreed that one more port should be opened per 5000 expected connection per second (cps)
>
> So here my results:
>
>
> Server:
> fireperf -s -P 10000 -p 63000:630010
>
> Client:
> fireperf -c <IP address> -P 1 -x -p 63000:63010 -> ~5000 cps
>
> fireperf -c <IP address> -P 10 -x -p 63000:63010 -> ~30000-35000 cps
>
> fireperf -c <IP address> -P 100 -x -p 63000:63010 -> ~35000-40000 cps
>
> fireperf -c <IP address> -P 1000 -x -p 63000:63010 -> ~40000-45000 cps
>
> fireperf -c <IP address> -P 10000 -x -p 63000:63010 -> ~46000-48000 cps
>
> The cpu utilization was limited to one core and increased in sync with the cps on both sides.
>
> In my last test, the utilization was about 85-100% on the server and 75-95% on the client.
>
> In the next days I will test our mini and post the results here.
>
> -
>
> Daniel
>
next prev parent reply other threads:[~2021-02-12 12:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <ae6acab7fc942043623641975f573525@ipfire.org>
2021-02-09 14:53 ` Michael Tremer
2021-02-12 12:30 ` Adolf Belka (ipfire-dev) [this message]
2021-02-12 12:34 ` Adolf Belka (ipfire-dev)
2021-02-15 16:08 ` Michael Tremer
2022-04-18 11:22 ` Fireperf: Adolf Belka
2021-02-16 11:48 ` Fireperf: first tests an results Michael Tremer
2021-02-16 12:16 ` Adolf Belka (ipfire-dev)
2021-02-16 15:00 ` Michael Tremer
2021-02-17 9:01 ` daniel.weismueller
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=e0545e4d-cce7-4869-c559-9efccfb1ee09@ipfire.org \
--to=adolf.belka@ipfire.org \
--cc=development@lists.ipfire.org \
/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