Skip to main content

Test NETWORK interface using iperf3

 C:\iperf3.5_64>iperf3 -c 172.168.1.100

warning: Ignoring nonsense TCP MSS -13312

Connecting to host 172.168.1.100, port 5201

[  5] local 192.168.8.101 port 52570 connected to 172.168.1.100 port 5201

[ ID] Interval           Transfer     Bitrate

[  5]   0.00-1.00   sec  6.88 MBytes  57.5 Mbits/sec

[  5]   1.00-2.00   sec  3.50 MBytes  29.4 Mbits/sec

[  5]   2.00-3.00   sec  4.00 MBytes  33.5 Mbits/sec

[  5]   3.00-4.01   sec  6.25 MBytes  52.0 Mbits/sec

[  5]   4.01-5.00   sec  4.75 MBytes  40.2 Mbits/sec

[  5]   5.00-6.01   sec  5.50 MBytes  45.9 Mbits/sec

[  5]   6.01-7.01   sec  5.88 MBytes  49.1 Mbits/sec

[  5]   7.01-8.00   sec  5.25 MBytes  44.3 Mbits/sec

[  5]   8.00-9.01   sec  5.88 MBytes  48.9 Mbits/sec

[  5]   9.01-10.00  sec  5.25 MBytes  44.4 Mbits/sec

- - - - - - - - - - - - - - - - - - - - - - - - -

[ ID] Interval           Transfer     Bitrate

[  5]   0.00-10.00  sec  53.1 MBytes  44.6 Mbits/sec                  sender

[  5]   0.00-10.13  sec  52.2 MBytes  43.3 Mbits/sec                  receiver


iperf Done.



this is to run client enviromnet.

Comments

Post a Comment

Popular posts from this blog

Warning: long redo log write elapsed times detected, the LG* process tracefiles have more details

Warning: long redo log write elapsed times detected, the LG* process tracefiles have more details This warning means LGWR / LGnn background processes are taking too long to write redo to the online redo logs. It is usually related to one of these: - Slow storage / high I/O latency on redo log disks - Redo logs placed on busy disks together with datafiles, FRA, archive logs, backups, or OS files - Too many commits from the application, causing frequent LGWR flushes - Redo log size too small, causing frequent log switches - CPU scheduling issue, where LGWR is not getting CPU quickly - Data Guard synchronous transport delay, if using SYNC/AFFIRM - In newer 19c RU versions, especially around 19.28, this warning can appear more visibly because of diagnostic changes, so first confirm whether there is a real performance impact before changing anything. - Oracle’s own wait-event documentation says log file sync is the foreground wait for redo write confirmation after commit, and log file paral...
Post a Comment
Read more

Convert TIMESTAMP to SCN and SCN to TIMESTAMP in Oracle

  Convert TIMESTAMP to SCN and SCN to TIMESTAMP in Oracle In many recovery scenario we need to know our SCN and timestamps. We can convert this by using the following function SCN_TO_TIMESTAMP TIMESTAMP_TO_SCN We can use this function with help of dual functions. Example of using this function as follows: 1. Convert the SCN to Timestamp SQL> select scn_to_timestamp(2011955) from dual; SCN_TO_TIMESTAMP(2011955) ----------------------------------------------------- 05-SEP-18 12.46.20.000000000 PM 2. Convert the Timestamp to SCN SQL> select timestamp_to_scn(to_timestamp('05-09-2018 12:46:21','dd-mm-yyyy hh24:mi:ss')) scn from dual; SCN ---------- 2011955
Post a Comment
Read more

How To Enable Flash Recovery Area In Oracle Database

  The flash recovery area(FRA) is an Oracle-managed destination( either FILE SYSTEM or ASM ) for centralized backup and recovery files. It simplifies the backup management. The following recovery-related files are stored in the flash recovery area: — Current control file — Online redo logs — Archived redo logs — Flashback logs — Control file auto backups — Datafile and control file copies — Backup pieces — Foreign archived redo log Below are the steps for enabling  flash  recovery area. DB_RECOVERY_FILE_DEST_SIZE   and  DB_RECOVERY_FILE_DEST   initial parameters are required for enabling FRA. DB_RECOVERY_FILE_DEST_SIZE   -> It is the disk quota size for the flash recovery area. DB_RECOVERY_FILE_DEST   – > This initialization parameter is a valid destination for the Flash Recovery Area. It can be a directory, file system, or ASM disk group. NOTE  : DB_RECOVERY_FILE_DEST_SIZE must be set before DB_RECOVERY_FILE_DEST. 1. Check whether FRA ...
Post a Comment
Read more