Upstream software project

libbenchmark-timer-perl

Benchmarking with statistical confidence

About libbenchmark-timer-perl

Benchmarking with statistical confidence

This project links 3 native package records across 3 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

Debian 12 (Bookworm): 1 package records; Debian 13 (Trixie): 1 package records; openSUSE Tumbleweed: 1 package records. Catalog coverage diagram, not an application screenshot.libbenchmark-timer-perl: recorded package coverageDebian 12 (Bookworm)1 recordsDebian 13 (Trixie)1 recordsopenSUSE Tumbleweed1 records
OpenFactory diagram of linked package records. It is not an application screenshot.

Project identity

Project
libbenchmark-timer-perl
Publisher
Not authoritatively mapped
Native package records
3
Operating systems
debian-12, debian-13, opensuse-tumbleweed
License expression
GPL-2.0-or-later
Source repository
Not reported

Source-reported description

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

The Benchmark::Timer class allows you to time portions of code conveniently, as well as benchmark code by allowing timings of repeated trials. It is perfect for when you need more precise information about the running time of portions of your code than the Benchmark module will give you, but don't want to go all out and profile your code. The methodology is simple; create a Benchmark::Timer object, and wrap portions of code that you want to benchmark with 'start()' and 'stop()' method calls. You can supply a tag to those methods if you plan to time multiple portions of code. If you provide error and confidence values, you can also use 'need_more_samples()' to determine, statistically, whether you need to collect more data. After you have run your code, you can obtain information about the running time by calling the 'results()' method, or get a descriptive benchmark report by calling 'report()'. If you run your code over multiple trials, the average time is reported. This is wonderful for benchmarking time-critical portions of code in a rigorous way. You can also optionally choose to skip any number of initial trials to cut down on initial case irregularities.

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.

Debian 12 (Bookworm)

  1. Package libbenchmark-timer-perl

    bookworm (Debian 12 (Bookworm)) (perl): benchmarking module with statistical confidence

    0.7112-2: all

Debian 13 (Trixie)

  1. Package libbenchmark-timer-perl

    trixie (Debian 13 (Trixie)) (perl): benchmarking module with statistical confidence

    0.7112-3: all

openSUSE Tumbleweed

  1. Package perl-Benchmark-Timer

    tumbleweed (openSUSE Tumbleweed) (Unspecified): Benchmarking with statistical confidence

    0.711.200-1.5: noarch

    Source: perl-Benchmark-Timer

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.