The old version was severely outdated, its HOMEPAGE is dead and its
build would break in an upcoming libssl change. Upstream has done a
lot of work, in particular idleconn now uses libevent/libeventextra.
Fixes a runtime failure reported by kevlo and Mikolaj Kucharski:
* Address issue where a test server may return an HTTP error during upload or download
* Address issue where ignore_ids may be empty or have empty values
ok kevlo sthen
if a port needs 2.x then set MODPY_VERSION=${MODPY_DEFAULT_VERSION_2}.
This commit doesn't change any versions currently used; it may be that
some ports have MODPY_DEFAULT_VERSION_2 but don't require it, those
should be cleaned up in the course of updating ports where possible.
Python module ports providing py3-* packages should still use
FLAVOR=python3 so that we don't have a mixture of dependencies some
using ${MODPY_FLAVOR} and others not.
Command-line benchmarking tool.
Features:
- Statistical analysis across multiple runs.
- Support for arbitrary shell commands.
- Constant feedback about the benchmark progress and current estimates.
- Warmup runs can be executed before the actual benchmark.
- Cache-clearing commands can be set up before each timing run.
- Statistical outlier detection to detect interference from other
programs and caching effects.
- Export results to various formats: CSV, JSON, Markdown, AsciiDoc.
- Parameterized benchmarks (e.g. vary the number of threads).
- Cross-platform
ok sthen@
OK sthen@
Comment:
network performance measurement tool
Description:
nuttcp is a network performance measurement tool intended for use
by network and system managers. Its most basic usage is to determine
the raw TCP (or UDP) network layer throughput by transferring memory
buffers from a source system across an interconnecting network to
a destination system, either transferring data for a specified time
interval, or alternatively transferring a specified number of bytes.
In addition to reporting the achieved network throughput in Mbps,
nuttcp also provides additional useful information related to the
data transfer such as user, system, and wall-clock time, transmitter
and receiver CPU utilization, and loss percentage (for UDP transfers).
workloads. fio will spawn a number of threads or processes doing a
particular type of IO action as specified by the user. It takes a
number of global parameters, each inherited by the thread unless other
parameters given to them overriding that setting. The typical use of
fio is to write a job file matching the IO load one wants to simulate.
okay sthen@
If somebody is removed who actually wants maintainer and either
didn't receive the mail, or didn't bother to reply to it, they are
free to send a diff to reinstate.
ok sthen@, jca@
some existing COMPILER lines with arch restrictions etc. In the usual
case this is now using "COMPILER = base-clang ports-gcc base-gcc" on
ports with c++ libraries in WANTLIB.
This is basically intended to be a noop on architectures using clang
as the system compiler, but help with other architectures where we
currently have many ports knocked out due to building with an unsuitable
compiler -
- some ports require c++11/newer so the GCC version in base that is used
on these archirtectures is too old.
- some ports have conflicts where an executable is built with one compiler
(e.g. gcc from base) but a library dependency is built with a different
one (e.g. gcc from ports), resulted in mixing incompatible libraries in the
same address space.
devel/gmp is intentionally skipped as it's on the path to building gcc -
the c++ library there is unused in ports (and not built by default upstream)
so intending to disable building gmpcxx in a future commit.
