You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@resilientdb.apache.org by "PNejr10 (via GitHub)" <gi...@apache.org> on 2026/05/29 04:20:07 UTC
[I] No automated way to detect PBFT performance regressions after code changes - ResPulse [incubator-resilientdb]
PNejr10 opened a new issue, #258:
URL: https://github.com/apache/incubator-resilientdb/issues/258
**Description**
Currently, there is no system in place to automatically detect when PBFT consensus performance degrades after a code change or configuration update. Developers and contributors have to manually run workloads, manually check metrics, and mentally piece together whether performance got worse and why. This creates a gap where regressions can go unnoticed until they impact production workloads.
Problem:
Performance regressions are not automatically detected after commits or merges
There is no baseline to compare current performance against
When performance does degrade, there is no explanation of what changed or why
Developers have to manually inspect multiple tools like ResView and ResLens to diagnose issues
**Motivation**
There needs to be a system that can answer three simple questions automatically:
**Did performance get worse?
What exactly changed?
Why do we think it changed?**
This issue tracks the need for an automated performance regression detection and explanation system built specifically for ResilientDB's PBFT consensus layer.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@resilientdb.apache.org.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] Proposal to add an automated way to detect PBFT performance regressions after code changes [incubator-resilientdb]
Posted by "Bismanpal-Singh (via GitHub)" <gi...@apache.org>.
Bismanpal-Singh closed issue #258: Proposal to add an automated way to detect PBFT performance regressions after code changes
URL: https://github.com/apache/incubator-resilientdb/issues/258
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@resilientdb.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org