diff --git a/benchmarks/stress-ng/Makefile b/benchmarks/stress-ng/Makefile index 185db03257a6..1311653fabf2 100644 --- a/benchmarks/stress-ng/Makefile +++ b/benchmarks/stress-ng/Makefile @@ -1,94 +1,94 @@ PORTNAME= stress-ng DISTVERSIONPREFIX= V DISTVERSION= 0.16.02 -PORTREVISION= 1 +PORTREVISION= 2 CATEGORIES= benchmarks MAINTAINER= pizzamig@FreeBSD.org COMMENT= Stress test benchmarks -WWW= http://kernel.ubuntu.com/~cking/stress-ng/ +WWW= https://github.com/ColinIanKing/stress-ng/ LICENSE= GPLv2+ LICENSE_FILE= ${WRKSRC}/COPYING LIB_DEPENDS+=libmpfr.so:math/mpfr USES= compiler:c11 gmake jpeg localbase:ldflags USE_GITHUB= yes GH_ACCOUNT= ColinIanKing ALL_TARGET= # empty PLIST_FILES= bin/stress-ng man/man1/stress-ng.1.gz OPTIONS_DEFINE= GPU JUDY LIBINOTIFY XXHASH OPTIONS_DEFINE_amd64= INTELIPSEC OPTIONS_DEFAULT= JUDY LIBINOTIFY XXHASH OPTIONS_DEFAULT_amd64= INTELIPSEC GPU_DESC= Enable support for GPU stressor (add GL) INTELIPSEC_DESC= Enable support for Intel's IPsec library JUDY_DESC= Enable support for (lib)Judy LIBINOTIFY_DESC= Enable support for libinotify XXHASH_DESC= Enable support for libxxhash INTELIPSEC_LIB_DEPENDS= libIPSec_MB.so:security/intel-ipsec-mb JUDY_LIB_DEPENDS= libJudy.so:devel/judy LIBINOTIFY_LIB_DEPENDS= libinotify.so:devel/libinotify LIBINOTIFY_LDFLAGS= -linotify XXHASH_LIB_DEPENDS= libxxhash.so:devel/xxhash XXHASH_LDFLAGS= -lxxhash GPU_USES= gl MAKE_ARGS= VERBOSE=1 .include .if ${PORT_OPTIONS:MGPU} USE_GL= egl glesv2 gbm .endif pre-patch: ${MKDIR} ${WRKSRC}/configs .if ${ARCH} == i386 ${TOUCH} ${WRKSRC}/configs/HAVE_VECMATH .endif #to dsiable Intel IPSEC detection post-patch-INTELIPSEC-off: ${TOUCH} ${WRKSRC}/configs/HAVE_LIB_IPSEC_MB ${TOUCH} ${WRKSRC}/configs/HAVE_INTEL_IPSEC_MB_H #to dsiable judy detection post-patch-JUDY-off: ${TOUCH} ${WRKSRC}/configs/HAVE_JUDY_H ${TOUCH} ${WRKSRC}/configs/HAVE_LIB_JUDY #to dsiable libinotify detection post-patch-LIBINOTIFY-off: ${TOUCH} ${WRKSRC}/configs/HAVE_INOTIFY ${TOUCH} ${WRKSRC}/configs/HAVE_SYS_INOTIFY # To disable libxxhash post-patch-XXHASH-off: ${TOUCH} ${WRKSRC}/configs/HAVE_LIB_XXHASH ${TOUCH} ${WRKSRC}/configs/HAVE_XXHASH_H post-patch-GPU-off: ${TOUCH} ${WRKSRC}/configs/HAVE_LIB_EGL ${TOUCH} ${WRKSRC}/configs/HAVE_EGL_H ${TOUCH} ${WRKSRC}/configs/HAVE_EGL_EXT_H ${TOUCH} ${WRKSRC}/configs/HAVE_LIB_GLES2 ${TOUCH} ${WRKSRC}/configs/HAVE_GLES2_H ${TOUCH} ${WRKSRC}/configs/HAVE_LIB_GBM ${TOUCH} ${WRKSRC}/configs/HAVE_GBM_H do-install: ${INSTALL_PROGRAM} ${WRKSRC}/stress-ng ${STAGEDIR}${PREFIX}/bin ${INSTALL_MAN} ${WRKSRC}/stress-ng.1 ${STAGEDIR}${MAN1PREFIX}/man/man1 .include diff --git a/benchmarks/stress-ng/pkg-descr b/benchmarks/stress-ng/pkg-descr index 16e6be5c6f6a..286a535651b8 100644 --- a/benchmarks/stress-ng/pkg-descr +++ b/benchmarks/stress-ng/pkg-descr @@ -1,4 +1,15 @@ -This stress test suite will stress a computer system in various -selectable ways It was designed to exercise various physical -subsystems of a computer as well as various operating system kernel -interfaces. +stress-ng will stress test a computer system in various selectable ways. It was designed to exercise various physical subsystems of a computer as well as the various operating system kernel interfaces. Stress-ng features: + + 300+ stress tests + 80+ CPU specific stress tests that exercise floating point, integer, bit manipulation and control flow + 20+ virtual memory stress tests + 40+ file system stress tests + 30+ memory/CPU cache stress tests + portable: builds on Linux (Debian, Devuan, RHEL, Fedora, Centos, Slackware OpenSUSE, Ubuntu, etc..), Solaris, FreeBSD, NetBSD, OpenBSD, DragonFlyBSD, Minix, Android, MacOS X, Serenity OS, GNU/Hurd, Haiku, Windows Subsystem for Linux and SunOs/Dilos/Solaris. with gcc, musl-gcc, clang, icc, icx, tcc and pcc. + tested on alpha, armel, armhf, arm64, hppa, i386, m68k, mips32, mips64, power32, ppc64el, risc-v, sh4, s390x, sparc64, x86-64 + +stress-ng was originally intended to make a machine work hard and trip hardware issues such as thermal overruns as well as operating system bugs that only occur when a system is being thrashed hard. Use stress-ng with caution as some of the tests can make a system run hot on poorly designed hardware and also can cause excessive system thrashing which may be difficult to stop. + +stress-ng can also measure test throughput rates; this can be useful to observe performance changes across different operating system releases or types of hardware. However, it has never been intended to be used as a precise benchmark test suite, so do NOT use it in this manner. + +Running stress-ng with root privileges will adjust out of memory settings on Linux systems to make the stressors unkillable in low memory situations, so use this judiciously. With the appropriate privilege, stress-ng can allow the ionice class and ionice levels to be adjusted, again, this should be used with care.