High-performance load testing tool
Features
- Protocol Agnostic - Currently supporting HTTP, HTTPS, HTTP/2.
- Scenario-Based - Create your flow in a JSON file. Without a line of code!
- Different Load Types - Test your system's limits across different load types.
===> The following configuration options are available for ddosify-2.6.0_24:
EMOJI=on: Enable emojis in console output
ZSH=on: Install programmable completions for zsh
===> Use 'make config' to modify these settings
Reason:
keep-alive is removed from config file. In default mode, the engine will use
keep-alive for all requests. If you want to disable keep-alive for a step, you
can add Connection: close header to the step.
Reason:
In 0.13.0 some configuration keys have been renamed for consistency. Have a
look at https://github.com/ddosify/ddosify/releases/tag/v0.13.0 for details.
go: Bump go124-dependent ports
Earlier I bumped the default Go to 1.24. Ports that specify a lower
version will still build with those lower version (for now), so they
don't need a bumping. Instead I'm bumping anything that (now) has go124
as a dependency.
benchmarks/ddosify: Mark BROKEN, deprecate and set expiration date to 2025-02-28
Fetch fails due to size mismatch and upstream has also renamed the
project to Anteon (https://github.com/getanteon/anteon)
x11-fonts/noto*: Restructure and update
Split x11-fonts/noto-basic into separate ports so they can be updated
separately. Keep noto-basic as a metaport but replace dependencies on
it with dependencies on individual fonts as needed.
Adjust x11-fonts/noto-extra to resolve conflicts for now. Individual
fonts can be split from this port later.
Let x11-fonts/noto-emoji install the monochrome Noto Emoji font and
create a new port x11-fonts/noto-color-emoji for Noto Color Emoji.
Add the new ports to x11-fonts/noto metaport and make Noto Sans and
Noto Serif non-optional because script-specific fonts depend on them.
(Only the first 15 lines of the commit message are shown above )
benchmarks/ddosify: Update to 1.0.3
ChangeLog: https://github.com/ddosify/ddosify/releases/tag/v1.0.3
* Update error msg
* Check status code for remote file on multipart
* Increase cpu time threshold on benchmark
PR: 271778
Reported by: 0xdutra@gmail.com (maintainer)
benchmarks/ddosify: Update to 0.15.0
ChangeLog: https://github.com/ddosify/ddosify/releases/tag/v0.15.0
Introducing engine modes:
engine_mode is optional in the config file.
* distinct-user mode simulates a new user for every iteration.
* repeated-user mode can use pre-used user in subsequent iterations.
* ddosify mode is the default mode of the engine. In this mode, the engine
runs in its max capacity, and does not show user simulation behavior.
Add breaking changes to UPDATING
PR: 270078
Reported by: 0xdutra@gmail.com (maintainer)
benchmarks/ddosify: Update to 0.13.0
ChangeLog: https://github.com/ddosify/ddosify/releases/tag/v0.13.0
* Merge remote-tracking branch 'origin/develop' into feat/concat-variables
* Update README.md
* change captureEnv to snake case
* change csv parameters to snake case
* change jsonPath to json_path
* fix done channel send place in stdoutJson
* get profile data from pprof package
* inject both typed and concatenated vars
* regexp, xpath, header_key
* remove unnecessary comment
* update benchmark jenkins file
* update jenkinsfile
* use atomic instead of mutex
PR: 269216
Reported by: 0xdutra@gmail.com (maintainer)
Remove WWW entries moved into port Makefiles
Commit b7f05445c00f has added WWW entries to port Makefiles based on
WWW: lines in pkg-descr files.
This commit removes the WWW: lines of moved-over URLs from these
pkg-descr files.
Approved by: portmgr (tcberner)
Add WWW entries to port Makefiles
It has been common practice to have one or more URLs at the end of the
ports' pkg-descr files, one per line and prefixed with "WWW:". These
URLs should point at a project website or other relevant resources.
Access to these URLs required processing of the pkg-descr files, and
they have often become stale over time. If more than one such URL was
present in a pkg-descr file, only the first one was tarnsfered into
the port INDEX, but for many ports only the last line did contain the
port specific URL to further information.
There have been several proposals to make a project URL available as
a macro in the ports' Makefiles, over time.
(Only the first 15 lines of the commit message are shown above )
benchmarks: remove 'Created by' lines
A big Thank You to the original contributors of these ports:
* Alexander Logvinov <ports@logvinov.com>
* Alexey Dokuchaev <danfe@FreeBSD.org>
* Alexey V. Degtyarev
* Andreas Kohn <andreas@syndrom23.de>
* Andrew Shevtsov <nyxo@dnuc.polyn.kiae.su>
* Andrey Zakhvatov <andy@FreeBSD.org>
* Andy Clark <andrewclarkii@gmail.com>
* Antonio Carlos Venancio Junior (<antonio@inf.ufsc.br>)
* Bill Fumerola <billf@chc-chimes.com>
* Brad Davis <brd@FreeBSD.org>
* Bruce A. Mah <bmah@FreeBSD.org>
(Only the first 15 lines of the commit message are shown above )
benchmarks/ddosify: Add new port
High-performance load testing tool
Features
- Protocol Agnostic - Currently supporting HTTP, HTTPS, HTTP/2.
- Scenario-Based - Create your flow in a JSON file. Without a line of code!
- Different Load Types - Test your system's limits across different load types.
WWW: https://github.com/ddosify/ddosify
PR: 264321
