iperf3 자체에서는 jumbo packet을 설정하는게 아니라
ifconfig를 통해 jumbo packet 크기로 MTU를 설정하면 된다.(1500 이상)
[링크 : http://www.packetinside.com/2012/03/jumbo-frame.html]
| iperf 파일로 바로바로 떨궈서 tail로 보기 (0) | 2025.02.10 |
|---|---|
| iperf3 (0) | 2023.07.28 |
| iperf udp 테스트 (0) | 2022.03.14 |
| iperf로 100M 랜 / IEEE1394 대역폭 측정 (2) | 2011.12.07 |
| iperf - 대역폭 측정 (0) | 2009.10.22 |
chatGPT 에게 물어보니 stdbuf라는걸 쓰라고
-o0 (소문자 오, 숫자 영) 을 하면 버퍼링 하지 않고 바로 보낸다.
| stdbuf - Run COMMAND, with modified buffering operations for its standard streams. Run COMMAND, with modified buffering operations for its standard streams. Mandatory arguments to long options are mandatory for short options too. -i, --input=MODE Adjust standard input stream buffering -o, --output=MODE Adjust standard output stream buffering -e, --error=MODE Adjust standard error stream buffering --help display this help and exit --version output version information and exit If MODE is 'L' the corresponding stream will be line buffered. This option is invalid with standard input. If MODE is '0' the corresponding stream will be unbuffered. |
[링크 : https://linux.die.net/man/1/stdbuf]
[링크 : https://blog.naver.com/5bpa/130167020787]
[링크 : https://knight76.tistory.com/entry/쉘에서-pipe-사용시-빨리-실행을-하도록-지원-stdbuf]
| iperf3 jumbo packet? (0) | 2025.02.15 |
|---|---|
| iperf3 (0) | 2023.07.28 |
| iperf udp 테스트 (0) | 2022.03.14 |
| iperf로 100M 랜 / IEEE1394 대역폭 측정 (2) | 2011.12.07 |
| iperf - 대역폭 측정 (0) | 2009.10.22 |
iperf/iperf2/ipef3 간에는 서로 호환성이 없는 듯. 기본 포트도 다르게 잡힌다.
크로스 컴파일
| /configure --build=i686-linux --host=arm-linux CC={크로스 컴파일러GCC 경로} CXX={크로스 컴파일러G++ 경로} |
[링크 : http://forum.falinux.com/zbxe/index.php?document_srl=869098&mid=lecture_tip]
대역폭 설정은 초당 얼마나 많은 데이터를 보내냐를 테스트 하는데 쓰이는데
| $ iperf3 --help Usage: iperf3 [-s|-c host] [options] iperf3 [-h|--help] [-v|--version] Server or Client: -p, --port # server port to listen on/connect to -f, --format [kmgtKMGT] format to report: Kbits, Mbits, Gbits, Tbits -i, --interval # seconds between periodic throughput reports -F, --file name xmit/recv the specified file -A, --affinity n/n,m set CPU affinity -B, --bind <host> bind to the interface associated with the address <host> -V, --verbose more detailed output -J, --json output in JSON format --logfile f send output to a log file --forceflush force flushing output at every interval --timestamps <format> emit a timestamp at the start of each output line (using optional format string as per strftime(3)) -d, --debug emit debugging output -v, --version show version information and quit -h, --help show this message and quit Server specific: -s, --server run in server mode -D, --daemon run the server as a daemon -I, --pidfile file write PID file -1, --one-off handle one client connection then exit --server-bitrate-limit #[KMG][/#] server's total bit rate limit (default 0 = no limit) (optional slash and number of secs interval for averaging total data rate. Default is 5 seconds) --rsa-private-key-path path to the RSA private key used to decrypt authentication credentials --authorized-users-path path to the configuration file containing user credentials Client specific: -c, --client <host> run in client mode, connecting to <host> --sctp use SCTP rather than TCP -X, --xbind <name> bind SCTP association to links --nstreams # number of SCTP streams -u, --udp use UDP rather than TCP --connect-timeout # timeout for control connection setup (ms) -b, --bitrate #[KMG][/#] target bitrate in bits/sec (0 for unlimited) (default 1 Mbit/sec for UDP, unlimited for TCP) (optional slash and packet count for burst mode) --pacing-timer #[KMG] set the timing for pacing, in microseconds (default 1000) --fq-rate #[KMG] enable fair-queuing based socket pacing in bits/sec (Linux only) -t, --time # time in seconds to transmit for (default 10 secs) -n, --bytes #[KMG] number of bytes to transmit (instead of -t) -k, --blockcount #[KMG] number of blocks (packets) to transmit (instead of -t or -n) -l, --length #[KMG] length of buffer to read or write (default 128 KB for TCP, dynamic or 1460 for UDP) --cport <port> bind to a specific client port (TCP and UDP, default: ephemeral port) -P, --parallel # number of parallel client streams to run -R, --reverse run in reverse mode (server sends, client receives) --bidir run in bidirectional mode. Client and server send and receive data. -w, --window #[KMG] set window size / socket buffer size -C, --congestion <algo> set TCP congestion control algorithm (Linux and FreeBSD only) -M, --set-mss # set TCP/SCTP maximum segment size (MTU - 40 bytes) -N, --no-delay set TCP/SCTP no delay, disabling Nagle's Algorithm -4, --version4 only use IPv4 -6, --version6 only use IPv6 -S, --tos N set the IP type of service, 0-255. The usual prefixes for octal and hex can be used, i.e. 52, 064 and 0x34 all specify the same value. --dscp N or --dscp val set the IP dscp value, either 0-63 or symbolic. Numeric values can be specified in decimal, octal and hex (see --tos above). -L, --flowlabel N set the IPv6 flow label (only supported on Linux) -Z, --zerocopy use a 'zero copy' method of sending data -O, --omit N omit the first n seconds -T, --title str prefix every output line with this string --extra-data str data string to include in client and server JSON --get-server-output get results from server --udp-counters-64bit use 64-bit counters in UDP test packets --repeating-payload use repeating pattern in payload, instead of randomized payload (like in iperf2) --username username for authentication --rsa-public-key-path path to the RSA public key used to encrypt authentication credentials [KMG] indicates options that support a K/M/G suffix for kilo-, mega-, or giga- iperf3 homepage at: https://software.es.net/iperf/ Report bugs to: https://github.com/esnet/iperf |
| iperf3 jumbo packet? (0) | 2025.02.15 |
|---|---|
| iperf 파일로 바로바로 떨궈서 tail로 보기 (0) | 2025.02.10 |
| iperf udp 테스트 (0) | 2022.03.14 |
| iperf로 100M 랜 / IEEE1394 대역폭 측정 (2) | 2011.12.07 |
| iperf - 대역폭 측정 (0) | 2009.10.22 |
흐음.. 로컬로 쐈는데 이정도면.. 성능 엄청 안 좋은건가?
아무튼 893번을 보내고 또 10번을 더 보내서 총 903번의 전송이 발생하는 것으로 보인다.
| $ iperf -u -p 16000 -c localhost ------------------------------------------------------------ Client connecting to localhost, UDP port 16000 Sending 1470 byte datagrams, IPG target: 11215.21 us (kalman adjust) UDP buffer size: 208 KByte (default) ------------------------------------------------------------ [ 3] local 127.0.0.1 port 49969 connected with 127.0.0.1 port 16000 [ ID] Interval Transfer Bandwidth [ 3] 0.0-10.0 sec 1.25 MBytes 1.05 Mbits/sec [ 3] Sent 893 datagrams [ 3] WARNING: did not receive ack of last datagram after 10 tries. |
[링크 : https://idchowto.com/iperf-를-이용한-네트워크-성능-측정/]
[링크 : https://chanind.github.io/2020/05/15/network-bandwidth-stress-testing-iperf.html]
+
i5-2520m 이고 로컬로 했는데 저조하네..
서버
| $ iperf -u -p 16000 -s localhost iperf: ignoring extra argument -- localhost ------------------------------------------------------------ Server listening on UDP port 16000 Receiving 1470 byte datagrams UDP buffer size: 208 KByte (default) ------------------------------------------------------------ [ 3] local 127.0.0.1 port 16000 connected with 127.0.0.1 port 59209 [ ID] Interval Transfer Bandwidth Jitter Lost/Total Datagrams [ 3] 0.0-10.0 sec 1.25 MBytes 1.05 Mbits/sec 0.003 ms 0/ 893 (0%) |
클라이언트
| $ iperf -u -p 16000 -c localhost ------------------------------------------------------------ Client connecting to localhost, UDP port 16000 Sending 1470 byte datagrams, IPG target: 11215.21 us (kalman adjust) UDP buffer size: 208 KByte (default) ------------------------------------------------------------ [ 3] local 127.0.0.1 port 59209 connected with 127.0.0.1 port 16000 [ ID] Interval Transfer Bandwidth [ 3] 0.0-10.0 sec 1.25 MBytes 1.05 Mbits/sec [ 3] Sent 893 datagrams [ 3] Server Report: [ 3] 0.0-10.0 sec 1.25 MBytes 1.05 Mbits/sec 0.000 ms 0/ 893 (0%) |
+
i7-10510U 라고 해도 별다를 건 없어 보이네?
서버
| $ iperf -u -p 16000 -s localhost iperf: ignoring extra argument -- localhost ------------------------------------------------------------ Server listening on UDP port 16000 Receiving 1470 byte datagrams UDP buffer size: 208 KByte (default) ------------------------------------------------------------ [ 3] local 127.0.0.1 port 16000 connected with 127.0.0.1 port 44436 [ ID] Interval Transfer Bandwidth Jitter Lost/Total Datagrams [ 3] 0.0-10.0 sec 1.25 MBytes 1.05 Mbits/sec 0.011 ms 0/ 893 (0%) |
클라이언트
| $ iperf -u -p 16000 -c localhost ------------------------------------------------------------ Client connecting to localhost, UDP port 16000 Sending 1470 byte datagrams, IPG target: 11215.21 us (kalman adjust) UDP buffer size: 208 KByte (default) ------------------------------------------------------------ [ 3] local 127.0.0.1 port 44436 connected with 127.0.0.1 port 16000 [ ID] Interval Transfer Bandwidth [ 3] 0.0-10.0 sec 1.25 MBytes 1.05 Mbits/sec [ 3] Sent 893 datagrams [ 3] Server Report: [ 3] 0.0-10.0 sec 1.25 MBytes 1.05 Mbits/sec 0.000 ms 0/ 893 (0%) |
+
-b 옵션을 통해 대역폭을 늘리니 cpu 사용율이 폭증한다.
| iperf3 jumbo packet? (0) | 2025.02.15 |
|---|---|
| iperf 파일로 바로바로 떨궈서 tail로 보기 (0) | 2025.02.10 |
| iperf3 (0) | 2023.07.28 |
| iperf로 100M 랜 / IEEE1394 대역폭 측정 (2) | 2011.12.07 |
| iperf - 대역폭 측정 (0) | 2009.10.22 |
| iperf3 jumbo packet? (0) | 2025.02.15 |
|---|---|
| iperf 파일로 바로바로 떨궈서 tail로 보기 (0) | 2025.02.10 |
| iperf3 (0) | 2023.07.28 |
| iperf udp 테스트 (0) | 2022.03.14 |
| iperf - 대역폭 측정 (0) | 2009.10.22 |
| iperf3 jumbo packet? (0) | 2025.02.15 |
|---|---|
| iperf 파일로 바로바로 떨궈서 tail로 보기 (0) | 2025.02.10 |
| iperf3 (0) | 2023.07.28 |
| iperf udp 테스트 (0) | 2022.03.14 |
| iperf로 100M 랜 / IEEE1394 대역폭 측정 (2) | 2011.12.07 |
|
