Hi Chris, SimpleConsensus has had issues in some scenarios, as far as I know. All of our tests, including the current integration tests, do not cover configurations using SimpleConsensus.
For edge deployments or a single-node setup with one ConfigNode and one DataNode, replacing Ratis with SimpleConsensus for SchemaRegions and ConfigNode consensus could improve the performance of some DDL statements. However, DDL operations are generally infrequent. For data writes, there is essentially no performance difference between SimpleConsensus and IoTConsensus V1. Both rely on the WAL, and IoTConsensus V1 does not incur additional replication overhead in a single-replica configuration. Best, Yuan On Sat, Nov 7, 2026 at 7:27 PM Christofer Dutz via dev <[email protected]> wrote: > Hi all, > > as I mentioned, I'm doing some experiments in my fork and one of them is > to make an Edge installation that is truly in-JVM verion. > So in order to see what improvements it brings, I had Claude run loads of > different benchmarks. > > In the end: For pure inserts the improvement is not that signifficant. > Howerver does Edge currently not use SimpleConsensus, So this is an > improvement IoTDB could quickly do. > > There is a noticable improvment with "management functions". > > I've had Claude summarize the findings here: > > https://claude.ai/artifact/T2SL24oeqPeS5rafHNEG67 > > Chris
