Flowgrind grinds flows among hosts in your network. It is a tool similar

to iperf, netperf to measure throughput and other metrics for TCP.
Flowgrind is split into two components: the flowgrind daemon and the
flowgrind controller. Using the controller, flows between any two systems
running the flowgrind daemon can be setup (third party tests). At regular
intervals during the test the controller collects and displays the
measured results from the daemons. It can run multiple flows at once with
the same or different settings and individually schedule every one.
Test and control connection can optionally be diverted to different interfaces.

WWW: http://launchpad.net/flowgrind

PR:		ports/176728
Submitted by:	Lars Eggert <lars@eggert.org>
This commit is contained in:
Beech Rintoul 2013-03-08 02:44:53 +00:00
parent d12657d8b5
commit ccc8dc4e23
Notes: svn2git 2021-03-31 03:12:20 +00:00
svn path=/head/; revision=313611
5 changed files with 43 additions and 0 deletions

View File

@ -16,6 +16,7 @@
SUBDIR += filebench
SUBDIR += fio
SUBDIR += flops
SUBDIR += flowgrind
SUBDIR += forkbomb
SUBDIR += geekbench
SUBDIR += gtkperf

View File

@ -0,0 +1,25 @@
# Created by: Lars Eggert <lars@eggert.org>
# $FreeBSD$
PORTNAME= flowgrind
PORTVERSION= 0.5.9
CATEGORIES= benchmarks
MASTER_SITES= http://launchpad.net/flowgrind/trunk/${PORTNAME}-${PORTVERSION}/+download/
MAINTAINER= lars@eggert.org
COMMENT= Measure throughput and other metrics for TCP
LIB_DEPENDS= xmlrpc++:${PORTSDIR}/net/xmlrpc-c \
gsl:${PORTSDIR}/math/gsl
BUILD_DEPENDS= ${LOCALBASE}/lib/libpcap.so:${PORTSDIR}/net/libpcap
USE_BZIP2= yes
GNU_CONFIGURE= yes
FETCH_ARGS= -pRr
MAN1= flowgrind-stop.1 \
flowgrind.1 \
flowgrindd.1
.include <bsd.port.pre.mk>
.include <bsd.port.post.mk>

View File

@ -0,0 +1,2 @@
SHA256 (flowgrind-0.5.9.tar.bz2) = 5a2dda682fc7b9040bc3c7df8f799801769c2c1f294cdce1ee37336f878379af
SIZE (flowgrind-0.5.9.tar.bz2) = 209124

View File

@ -0,0 +1,11 @@
Flowgrind grinds flows among hosts in your network. It is a tool similar
to iperf, netperf to measure throughput and other metrics for TCP.
Flowgrind is split into two components: the flowgrind daemon and the
flowgrind controller. Using the controller, flows between any two systems
running the flowgrind daemon can be setup (third party tests). At regular
intervals during the test the controller collects and displays the
measured results from the daemons. It can run multiple flows at once with
the same or different settings and individually schedule every one.
Test and control connection can optionally be diverted to different interfaces.
WWW: http://launchpad.net/flowgrind

View File

@ -0,0 +1,4 @@
@comment $FreeBSD$
bin/flowgrind
bin/flowgrind-stop
sbin/flowgrindd