feat(docs): performance_eval (#128)

* Initial draf of performance evaluation

* removed full screengrabs

* add performance eval to docs summary

* update Malachite perf section

* add notes to docs

* update emerald perf eval

* update bytes units

* bare metal results

* Added performance data fro geodistributed run

* Reworded load generation stats

* remove old figures

* update performance doc

* fix typo

* remove extra figures

* fix TODOs

* update figure

* rename perform eval file

* update readme

---------

Co-authored-by: Marius Poke <marius.poke@posteo.de>

Author: jmalicevic

README.md

@@ -64,7 +64,12 @@ For instructions on how to launch an Emerald network in production, please refer
 
 ## Performance Evaluation
 
-> TODO: some performance number and link to how to run benchmarks
+Emerald delivers high performance with sub-second block times, providing the low-latency confirmations needed for demanding institutional applications. 
+In benchmarking, Emerald reaches approximately 9,200 TPS peak and 8,300 TPS sustained. 
+Its consensus engine, Malachite, can achieve up to 71.7k TPS without an execution client, 
+demonstrating both the strength of the underlying consensus layer and the clear potential to further optimize Emerald. 
+
+For more details, please refer to the [Performance Evaluation](https://emerald-docs.informalsystems.io/performance_evaluation/index.html) section of the docs.
 
 ## Contributing
 

app/src/app.rs

@@ -31,7 +31,6 @@ use crate::state::{assemble_value_from_parts, decode_value, extract_block_header
 use crate::sync_handler::{get_decided_value_for_sync, validate_payload};
 
 pub async fn initialize_state_from_genesis(state: &mut State, engine: &Engine) -> eyre::Result<()> {
-    // TODO Unify this with code above @Jasmina
     // Get the genesis block from the execution engine
     let genesis_block = engine
         .eth

docs/operational-docs/src/SUMMARY.md

@@ -8,7 +8,7 @@
 
 ---
 
-# Architecture
+# Core Concepts
 
 
 - [Architecture](./architecture/index.md)
@@ -18,7 +18,7 @@
 
 ---
 
-# Guides
+# Run & Deploy
 
 - [Deploy Local Testnet](local-devnet/index.md)
   - [Creating a Testnet](local-devnet/create-network.md)
@@ -35,10 +35,10 @@
   - [Creating Network Genesis](production-network/genesis.md)
   - [Running Reth](production-network/running-reth.md)
   - [Running Emerald](production-network/running-emerald.md)
+- [Configuration Examples](./config-examples.md)
 
 ---
 
-# References 
-
-- [Configuration Examples](./config-examples.md)
+# Performance
 
+- [Performance Evaluation](./performance_evaluation/index.md)

docs/operational-docs/src/architecture/consensus.md

@@ -10,12 +10,13 @@ which is the most battle-tested consensus protocol in blockchain today.
 
 **Single-Slot Finality.** Transactions are finalized immediately once blocks are committed, without the risk of reorgs.
 
-**Low Latency.** Malachite finalizes blocks in under one second, delivering the low-latency confirmation times required for high-performance institutional applications.
+**Formally Specified.** Malachite was formally specified using the [Quint specification language](https://quint-lang.org). 
 
-**High Throughput.** 
- > TODO: add throughput results 
+**Low Latency.** Malachite finalizes blocks in under one second, delivering the low-latency confirmation times required for high-performance institutional applications.
 
-**Formally Specified.** Malachite was formally specified and model checked using the [Quint specification language](https://quint-lang.org). 
+**High Throughput.** Malachite without an Ethereum execution client on top can reach up to 71.7k TPS for single datacenter deployments and up to 41.4k TPS for geo-distributed deployments. 
+When deploying with Reth as an execution client, Emerald achieves around 9,200 TPS peak and 8,300 TPS sustained on a single datacenter deployment.
+This demonstrates both the strength of the underlying consensus engine and the clear potential to further optimize Emerald.
 
 ## Malachite Integration 
 
@@ -32,7 +33,11 @@ Emerald, as a Malachite application, only needs to interact with the consensus e
 
 - `AppMsg::Decided { certificate, reply }`: Notifies the application that consensus has been reached, providing a certificate with the decided value and supporting votes.
 
-**Note.** Emerald doesn't currently support the following Malachite events: `AppMsg::RestreamProposal` , `AppMsg::ExtendVote`, `AppMsg::VerifyVoteExtension`.
+> [!NOTE]
+> Emerald doesn't currently support the following Malachite events: 
+> - `AppMsg::RestreamProposal`
+> - `AppMsg::ExtendVote`
+> - `AppMsg::VerifyVoteExtension`
 
 ## Additional Features