[Testing] Add Notification Processing Stress Tests

[Abd-Standard]

Description

Create stress tests that evaluate NotifyChain's behavior under sustained, high-volume notification traffic. The goal is to identify bottlenecks and ensure the system remains stable under heavy workloads.

Tasks
Simulate continuous notification traffic.
Measure throughput and latency.
Record resource utilization.
Document benchmark results.
Integrate tests into the CI pipeline where applicable.

Acceptance Criteria
Stress tests execute successfully.
Benchmark results are documented.
System stability is verified under load.
Test reports are reproducible.

Contributors start work by running:
git checkout -b tests/stress-notification-processing

[Jaydearcadian]

Hey, I'd like to take this on.

For stress tests to actually be useful, the benchmarks need to report more than just throughput. I'd make sure the results include p50/p95/p99 latency alongside notifications per second, so bottlenecks show up clearly rather than getting averaged away. Resource utilization (CPU, memory, queue depth if applicable) would be captured per run so the reports are reproducible in CI and comparable across future changes.

I'd get a PR ready in 24hours

[GBOYEE]

Hey! The stress test issue is pretty straightforward. I can write a load test that hammers the notification queue with sustained traffic — measure throughput, catch where latency spikes, and document the breaking point. The existing test helpers in tests/ already mock the notification pipeline, so I can build on that instead of starting from scratch. Mind if I grab this? I will have a draft PR up by tomorrow.

[YfengJ]

Hi maintainers, I would like to apply for this issue if it is still available.

If assigned, I will keep the PR focused on a reproducible notification-processing stress suite: simulate sustained notification traffic through the existing test/helpers, report throughput plus p50/p95/p99 latency, document how to rerun the benchmark locally or in CI, and avoid changing runtime delivery semantics outside the test/support surface.

[Ayinkx01]

Hi l would like to take this job

[Luchistack]

Hi Maintener, I would love to work on this issue.

[David-282]

Kindly assgun this issue to me

[Truphile]

Hi team, I’d love to take this on!

As a returning contributor, I’m already familiar with the repository workflow and setup. This is right up my field I’ve implemented very similar architectural patterns and requirements before.

I’ve reviewed the acceptance criteria and can deliver a clean, well-tested solution immediately. Ready for assignment!

[MztaKing]

Dear Team, I will appreciate the opportunity to work on this issue.
Kind Regards

[LuisD-Dev]

Hi, I’d like to work on this issue. I’ve reviewed the description and I believe I can handle the implementation.

Could you please assign it to me? Once it is assigned, I’ll start working on it and submit a pull request with the corresponding changes.

Thank you!

[Scepter00]

Hi! I'd like to take on this issue.

I have experience writing automated tests and benchmarking application performance, and I'm interested in helping validate NotifyChain's behavior under sustained load. My approach will be to create stress tests that simulate continuous notification traffic, measure throughput and latency, and capture resource utilization to identify any performance bottlenecks.

I'll document the benchmark methodology and results, make sure the tests produce reproducible reports, and integrate them into the CI pipeline where appropriate so performance can be monitored consistently.

I'll begin by creating the branch specified in the issue:

git checkout -b tests/stress-notification-processing

I'd be happy to work on this.

[Purity-Euphemia]

Good Day Maintainer, I have experience and would review the issue, implement a clean solution, test it, and submit a pull request.

[Purity-Euphemia]

Good Day Maintainer, I have experience and would review the issue, implement a clean solution, test it, and submit a pull request.