Add benchmark harness: logfwd vs vector vs filebeat#4
Merged
Conversation
Introduces bench/run.sh which routes all three log agents through a shared logfwd blackhole HTTP sink for apples-to-apples throughput comparison. Supports configurable line counts and selective agent runs. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
4 tasks
This was referenced Apr 20, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
bench/run.sh, a benchmark harness that compares logfwd, vector, and filebeat throughput--linesto configure workload size and--agentsto selectively run specific agentsTest plan
./bench/run.sh --lines 100000 --agents logfwdto verify logfwd-only path works./bench/run.sh --agents logfwd,vectorto verify multi-agent comparison🤖 Generated with Claude Code