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.
Do it for all packages that
* mention perl, or
* have a directory name starting with p5-*, or
* depend on a package starting with p5-
like last time, for 5.18, where this didn't lead to complaints.
Let me know if you have any this time.
*) Initial pass at support for --enable-intervals (WANT_INTERVALS) for
Windows, courtesy of Jonathan Cook.
*) When in demo mode (./configure --enable-demo and a global -D
<interval> option netperf will make sure it emits "one last
interval result" when the test is terminated. This should assist
when post-processing results through the likes of rrdtool when
there is a slow-down in the performance just at the end that would
have stretched the interval to beyond the test termination.
*) A fix to have the AF_UNIX tests realize that the value for "take
the system default" socket buffer size became -1 years ago. Bug
found by Eric Dumazet.
*) Include a patch from Dave Taht to enable symbolic manipulation of
IP_TOS values.
*) Include a patch from Sachar Raindel to enable the omni tests to get
ENOBUFS under Linux when the socket buffer is larger than the tx
queue of the egress interface. This will help preclude netperf's
reporting a larger than link-rate send-side figure.
*) Fix a problem with late checking of the return from select() in
src/netserver.c. Reported by Waqar Sheikh.
*) A new global -Z option has been added to netperf and netserver.
This takes as an argument a passphrase. In the case of netserver
it will expect a control message with the passphrase as the first
thing it receives on the control connection. If netserver does not
receive a control message with the passphrase it will close the
control connection and move-on. If the netserver receives a
control message with a passprhase when it is not lookign for one,
it will be ignored. There is at present a 20 second timeout on the
attempted receipt of the request message. In the case of netperf,
the passphrase will be the first thing sent on the control
connection. There is no response to a passphrase control message.
*) Demo mode output format will now track the omni output format. So,
if the omni ouput format is CSV then the interim results will be
emitted in csv. Likewise for keyval. If the mode is human (default
and test-specific -O) then the output remains unchanged. Keyval
output includes the count of interval, with a mind towards being
able to source it in shells and whatnot. Subject to change without
notice.
*) A patch to correctly handle IPv6 addresses in the control messages,
courtesy of Bjoern Zeeb.
*) The global -F option can now be used specify a local and/or remote
fill file.
*) It is now possible to set/get the TCP congestion control algorithm
being used by either end of the test connection when using the omni
code. The output selectors are LOCAL_CONG_CONTROL and
REMOTE_CONG_CONTROL and setting is via the test-specific -K option.
*) Stop leaking file descriptors when looking-up probable egress
interface names and I/O slot numbers.
*) The global -Y option can be used to set IP_TOS on those platforms
which support it. Since this is specific to IP (v4 or v6) it may
move to a test-specific otion in the future. It is presently
global for foolish consistency with the -y option to set
SO_PRIORITY.
*) The global -y option can be used to set SO_PRIORITY on those
platforms which support it. Based on patches from Amir Vidai.
*) The control message size has been increased from 256 bytes to 512
bytes. THIS WILL BREAK COMPATABILITY WITH PREVIOUS VERSIONS OF
NETPERF. However, we need more room on the pinhead on which the
angels dance.
*) Make the "sum" field of the histogram structure a 64 bit int to
avoid having it wrap-around on tests where the sum of all the
measured latencies was larger than 31 bits. This was causing
statistics like stddev to go negative in some cases.
*) If the time delta between two events is negative, do not bother
doing any math with it in the histogram/statistics code, just
increment the ridiculous count and move-on.
*) Fixed a bug which caused local transport retransmissions to be
reported as -1 even though the getsockopt() call was
successful. (Linux). Later included remote transport
retransmissions.
*) The src/nettest_omni.c and re-written src/netserver.c code are now
known to have compiled under Windows 7 x64 with the Microsoft
WDK. There remains a timing issue with confidence intervals which
is yet to be addressed, and may have been there for ages. Netserver
has been run as a non-spawning (-f) server, netperf has been run,
both have run "classic" and "omni" tests.
1.) Comment out "MASTER_SITES". The URL no longer works and all copies
that Google can find are "pkgsrc" distfile mirrors.
2.) Fix various "pkglint" errors.
DNSPerf, ResPerf, and DHCPerf are free tools developed by Nominum that
make it simple to gather accurate latency and throughput metrics for
Domain Name Service (DNS) and Dynamic Host Configuration Protocol
(DHCP). These tools are easy-to-use and simulate typical Internet so
network operators can benchmark their naming and addressing
infrastructure and plan for upgrades. The latest version of the DNS
test tools (DNSPerf and ResPerf) can be used with new test files that
include IPv6 queries.
DNSPerf "self-paces" the DNS query load to simulate network
conditions. New features in DNSPerf improve the precision of latency
measurements and allow for per packet per-query latency reporting is
possible. DNSPerf is now multithreaded, multiple DNSPerf clients can
be supported in multicore systems (each client requires two
cores). The output of DNSPerf has also been improved so it is more
concise and useful. Latency data can be used to make detailed graphs
so it is simple for network operators to take advantage of the data.
The point of paranoia is to assess a compiler/machine environment.
Therefore, this package should be built with the default CFLAGS, and
not add options to try to get the tests to pass. This will cause
errors to be reported on i386.
Take MAINTAINERSHIP.
to address issues with NetBSD-6(and earlier)'s fontconfig not being
new enough for pango.
While doing that, also bump freetype2 dependency to current pkgsrc
version.
Suggested by tron in PR 47882
a) refer 'perl' in their Makefile, or
b) have a directory name of p5-*, or
c) have any dependency on any p5-* package
Like last time, where this caused no complaints.
File too long (should be no more than 24 lines).
Line too long (should be no more than 80 characters).
Trailing empty lines.
Trailing white-space.
Trucated the long files as best as possible while preserving the most info
contained in them.
RAMspeed, a cache and memory benchmarking tool
(for uniprocessor machines running UNIX-like operating systems).
This command line utility measures effective bandwidth of both cache and memory
subsystems. It has been written entirely in C for portability purposes, though
benchmark routines are also available in several assembly languages for
performance reasons.
The "-r" option is highly discouraged in BSD although it's reluctantly
supported. The problem is that it doesn't behave the same on all
platforms. For example, "cp -r pts-core/ destdir/" won't always give
the same results:
On NetBSD, pts-core files are put: /destdir/pts-core/<files>
On DragonFly pts-core files are put: /destdir/<files>
That messes the PLIST up.
This changes "cp -r <dir>/" to "cp -R <dir>" which has the same
behavior on different platforms. Tested on NetBSD and DragonFly
