GyulyVGC/sniffnet

Benchmark Sniffnet performance

Open

#489 opened on Mar 30, 2024

View on GitHub
 (3 comments) (2 reactions) (0 assignees)Rust (37,468 stars) (1,509 forks)batch import
good first issuehelp wantedtesting

Description

This issue wants to track the need for a benchmark to accurately measure the speed of the app, measured in packets per second (pps) that can be handled without dropping frames.

This is necessary to find out ways that can help improving the performance even further.

Today I tried testing Sniffnet with iperf on a different machine and I could observe that the current packets per second limit is higher than 100k:

Screenshot 2024-01-09 at 12 26 24

Originally discussed in #373

Contributor guide

Tech stack
rust
Domain
performance
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
Rust programmingbasic networkingbenchmarking concepts
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
50
Research direction
Implement a performance benchmark using Rust's `criterion` crate to measure packets per second (pps). Start by examining the main packet processing loop in `src/` directory. The benchmark should simulate network traffic using `iperf` or pre recorded pcap files. Discuss in the issue any questions about test conditions.