{"schema_version":1,"metadata":{"branch":"current","release":"7.9","architecture":"amd64","generated_at":"2026-09-09T04:04:41.004595+00:00","source_url":"https://cdn.openbsd.org/pub/OpenBSD/snapshots/packages/amd64/sqlports-7.55.tgz","source_sha256":"fcdbba1b9df747882aa9bab4af20ebec8dac10655069c90f1cd4145c06e1235e","package_count":12031,"source_kind":"sqlports"},"package":{"name":"netpipe-3.7.2","path":"benchmarks/netpipe","url":"/packages/current/benchmarks/netpipe/","comment":"self-scaling network benchmark","homepage":"http://bitspjoule.org/netpipe/","maintainer":"The OpenBSD ports mailing-list <ports@openbsd.org>","description":"NetPIPE is a protocol independent performance tool that encapsulates\nthe best of ttcp and netperf and visually represents the network\nperformance under a variety of conditions. By taking the end-to-end\napplication view of a network, NetPIPE clearly shows the overhead\nassociated with different protocol layers. Netpipe answers such\nquestions as: how soon will a given data block of size k arrive at its\ndestination? Which network and protocol will transmit size k blocks\nthe fastest? What is a given network's effective maximum throughput\nand saturation level?  Does there exist a block size k for which the\nthroughput is maximized? How much communication overhead is due to the\nnetwork communication protocol layer(s)? How quickly will a small (< 1\nkbyte) control message arrive, and which network and protocol are best\nfor this purpose?\n\nFor a paper fully describing NetPIPE and sample investigation of\nnetwork performance issues using NetPIPE, see\nhttp://www.scl.ameslab.gov/netpipe/paper/full.html.\n","package_architecture":"amd64","stem":"netpipe","readme":null,"dependencies":[],"reverse_dependencies":{"count":0,"url":null},"categories":["benchmarks","net"],"flavors":[],"only_for_architectures":[],"not_for_architectures":[]}}