Upstream software project

uperf

Unified Network Performance Tool

About uperf

Unified Network Performance Tool

This project links 5 native package records across 5 recorded operating-system releases. Compare the retained versions and architectures below, then open the package for your own release.

These are catalog observations, not a guarantee of installation, compatibility, or upstream support.

Project pictures and package coverage

Fedora 43: 1 package records; Fedora 44: 1 package records; openSUSE Leap 15.6: 1 package records; openSUSE Leap 16.0: 1 package records; openSUSE Tumbleweed: 1 package records. Catalog coverage diagram, not an application screenshot.uperf: recorded package coverageFedora 431 recordsFedora 441 recordsopenSUSE Leap 15.61 recordsopenSUSE Leap 16.01 recordsopenSUSE Tumbleweed1 records
OpenFactory diagram of linked package records. It is not an application screenshot.

Project identity

Project
uperf
Publisher
Not authoritatively mapped
Native package records
5
Operating systems
fedora-43, fedora-44, opensuse-leap-15-6, opensuse-leap-16-0, opensuse-tumbleweed
License expression
GPL-3.0-only
Source repository
Not reported

Source-reported description

The fullest retained description is shown with its source. Distribution packaging descriptions may include downstream details.

uperf is a network performance tool that supports modelling and replay of various networking patterns. uperf was developed by the Performance Applications Engineering group at Sun Microsystems and is released under the GNU General Public License Version 3. uperf represents the next generation benchmarking tools (like filebench) where instead of running a fixed benchmark or workload, a description (or model) of the workload is provided and the tool generates the load according to the model. By distilling the benchmark or workload into a model, you can now do various things like change the scale of the workload, change different parameters, change protocols, etc and analyse the effect of these changes on your model. You can also study the effect of interleaving CPU activity, or think times or the use of SSL instead of TCP among many other things. Some of the questions you could answer using uperf are * Bandwidth and latency (unidirectional and bi-directional) with different protocols like TCP, UDP, SCTP, SSL * Connection setup and teardown scalability for different protocols * Effect of noise on ongoing network connections * Does it matter if I use processes instead of threads to do network communication? * What is the L2 cache miss rate for connection setup? * Understand TCP, UDP, SCTP, SSL performance under a variety of conditions and much more!

Description source

Packages by operating system

Compare recorded versions, then open a package for dependency, file, checksum, and repository evidence. Version strings are distribution-specific, not a ranking of newer software.

Fedora 43

  1. Package uperf

    43 (Fedora 43) (Unspecified): Network performance tool with modelling and replay support

    1.0.8-7.fc43: aarch64 x86_64

    Source: uperf

Fedora 44

  1. Package uperf

    44 (Fedora 44) (Unspecified): Network performance tool with modelling and replay support

    1.0.8-8.fc44: aarch64 x86_64

    Source: uperf

openSUSE Leap 15.6

  1. Package uperf

    leap-15.6 (openSUSE Leap 15.6) (Productivity/Networking/Diagnostic): Unified Network Performance Tool

    1.0.7-bp156.3.7: aarch64 ppc64le s390x x86_64

    Source: uperf

openSUSE Leap 16.0

  1. Package uperf

    leap-16.0 (openSUSE Leap 16.0) (Productivity/Networking/Diagnostic): Unified Network Performance Tool

    1.0.8-bp160.1.12: aarch64 ppc64le s390x x86_64

    Source: uperf

openSUSE Tumbleweed

  1. Package uperf

    tumbleweed (openSUSE Tumbleweed) (Productivity/Networking/Diagnostic): Unified Network Performance Tool

    1.0.8-1.9: x86_64

    Source: uperf

Project resources and further reading

Mapping provenance

Only source-backed identity signals create public cross-OS links. A reviewer can later approve or dispute an inferred relationship without rewriting native package history.

No field-level source record is published yet.