[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

[victor62-art]

pls assign me this issue

[clintjeff2]

Hello, I have 6 years of experience working on tasks like this and handling similar challenges across backend, frontend, and smart-contract development. I have carefully read and fully understood the task requirements, and I am confident I can deliver a clean, efficient, and well-tested solution promptly. I always ensure high-quality implementation, maintainability, and adherence to best practices.

Pull request in 5 hours.

[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.