iperf3

{
  "aliases": [],
  "alternatives": [
    "netperf",
    "nuttcp",
    "ping",
    "iftop",
    "nethogs"
  ],
  "build_dependencies": [],
  "categories": [
    "networking",
    "benchmark"
  ],
  "caveats": null,
  "conflicts_with": [],
  "dependencies": [
    "openssl@4"
  ],
  "deprecated": 0,
  "deprecation_reason": null,
  "desc": "Update of iperf: measures TCP, UDP, and SCTP bandwidth",
  "disable_reason": null,
  "disabled": 0,
  "enrichment_fetched_at": "2026-06-20T23:38:54+00:00",
  "first_seen": "2026-06-20T23:34:18+00:00",
  "full_name": "iperf3",
  "github_default_branch": "master",
  "github_last_commit_at": "2026-06-12T23:16:40Z",
  "github_readme_excerpt": "iperf3:  A TCP, UDP, and SCTP network bandwidth measurement tool\n================================================================\n\nSummary\n-------\n\niperf is a tool for active measurement of the maximum achievable\nbandwidth on IP networks.  It supports tuning of various parameters\nrelated to timing, protocols, and buffers.  For each test it reports\nthe measured throughput / bitrate, loss, and other parameters.\n\nThis version, sometimes referred to as iperf3, is a redesign of an\noriginal version developed at NLANR/DAST.  iperf3 is a new\nimplementation from scratch, with the goal of a smaller, simpler code\nbase, and a library version of the functionality that can be used in\nother programs. iperf3 also has a number of features found in other tools\nsuch as nuttcp and netperf, but were missing from the original iperf.\nThese include, for example, a zero-copy mode and optional JSON output.\nNote that iperf3 is *not* backwards compatible with the original iperf.\n\nOne of the primary uses for iperf3 is as a component of the perfSONAR\nnetwork measurement system (https://www.perfsonar.net/). It is also\nuseful as a standalone tool, and is used as such by ESnet and other\nR\u0026E networks. It has also been found useful in the general networking\ncommunity and has even found its way into various commercial products.\n\nPrimary development for iperf3 takes place on Ubuntu Linux, FreeBSD,\nand macOS.  At this time, these are the only officially supported\nplatforms, however there have been some reports of success with\nOpenBSD, NetBSD, Android, Solaris, and other Linux distributions.\n\niperf3 is principally developed by ESnet / Lawrence Berkeley National\nLaboratory.  It is released under a three-clause BSD license.\n\nFor more information see: https://software.es.net/iperf\n\nSource code and issue tracker: https://github.com/esnet/iperf\n\nDiscussion forums: https://github.com/esnet/iperf/discussions\n\nReporting security vulnerabilities: iperf@es.net\n\nFrequently Asked Questions: https://software.es.net/i",
  "github_repo": "esnet/iperf",
  "github_stars": 8548,
  "github_topics": [
    "iperf3"
  ],
  "homepage": "https://github.com/esnet/iperf",
  "homepage_og_description": null,
  "homepage_og_image": null,
  "homepage_title": null,
  "installs_30d": 6242,
  "installs_365d": 85342,
  "installs_90d": 28452,
  "keg_only": 0,
  "keg_only_reason": null,
  "last_seen": "2026-06-20T23:34:18+00:00",
  "license": "BSD-3-Clause",
  "llm_generated_at": "2026-06-20T23:45:19+00:00",
  "llm_model": "claude-haiku-4-5",
  "name": "iperf3",
  "oldnames": [],
  "one_liner": "Network bandwidth measurement tool for TCP, UDP, and SCTP connections with JSON output and zero-copy mode.",
  "optional_dependencies": [],
  "rank_30d": 510,
  "rank_365d": 472,
  "rank_90d": 407,
  "raw_hash": "8f66356aad3f5d93",
  "recommended_dependencies": [],
  "revision": 1,
  "ruby_source_path": "Formula/i/iperf3.rb",
  "tap": "homebrew/core",
  "test_dependencies": [],
  "uses_from_macos": [],
  "version_head": "HEAD",
  "version_stable": "3.21",
  "versioned_formulae": [],
  "why_use_this": "iperf3 measures maximum achievable bandwidth between two hosts with tunable protocol parameters, timing, and buffers. It\u0027s the standard for network performance testing, especially in research and enterprise environments, and offers a library API for embedding in other tools. Choose it over netperf or nuttcp for cleaner code, smaller footprint, and straightforward client-server architecture."
}