Date: Tue, 30 Apr 2019 11:20:42 +0700 From: Eugene Grosbein <eugen@grosbein.net> To: Alan Somers <asomers@freebsd.org> Cc: Wojciech Puchar <wojtek@puchar.net>, "freebsd-hackers@freebsd.org" <freebsd-hackers@freebsd.org> Subject: Re: very low performance tcp/rsh Message-ID: <2da04de7-2e41-2521-8570-18bf3d5ee2c5@grosbein.net> In-Reply-To: <CAOtMX2hAeq%2B7GwdXu9MptrMk%2BY%2B37zebTU%2Bn41j0NT5-UVz53Q@mail.gmail.com> References: <alpine.BSF.2.20.1904292028400.48623@puchar.net> <ef440d5f-c543-148a-4e68-44b0bc62b28f@grosbein.net> <alpine.BSF.2.20.1904292111080.57162@puchar.net> <cb76aa41-1472-5df1-5b24-384f6453f3de@grosbein.net> <CAOtMX2hAeq%2B7GwdXu9MptrMk%2BY%2B37zebTU%2Bn41j0NT5-UVz53Q@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
30.04.2019 3:08, Alan Somers wrote: > Better yet, if the goal is simply to measure TCP performance, use > benchmarks/netperf. Don't try to do anything involving files. I have not tried netperf. Is it better than iperf abusing kernel with tons of gettimeofday() system calls (linux-style)? For slow speeds it does not matter but this is very bad for high speed benchmarking.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?2da04de7-2e41-2521-8570-18bf3d5ee2c5>