---
# System prepended metadata

title: Validator NOM Performance

---

---
title: Node Operator Performance Metrics
description: Criteria for Node Operator Selection
version: April 24, 2024
---

# Validator NOM Performance 

This is for LST's in general, and not specific to any one LST or Node Operator.


e. The only exceptions are peers with
1 and 2 vCPUs that are CPU-bottlenecked, having more
than 90% CPU utilization

 Processing transactions within a channel
- To achieve higher throughput and lower latency, it is better to allocate at least one vCPU per channel. For
optimal vCPU allocation, we need to determine the expected
load at each channel and allocate adequate vCPUs accordingly.
- To achieve higher throughput and lower
latency, it is better to avoid heterogeneous peers as the
performance would be dictated by less powerful peers.



## General Statistics
### Number of Node Operators (NO)
### Active Validators
### Avg. Keys per Node Operator
### Number of validator public keys funded
### Avg. Validator Keys per Beacon Node*
### Validators Activated
### Avg. Validator Keys per Execution Client*
### Validators Exited

### Missed Blocks %
### Missed Blocks
### Proposer Duties

### Attester Effectiveness
### Proposer Effectiveness

### APR%
### Consensus APR%
### Execution APR%

### Consensus Layer Client Distribution
### Execution Layer Client Distribution

### Hosting Provider Client Distribution

### MEV

#### MEV Relay distribution
- USM
- Flashbots
- Bloxroute
- Agnostic
- Aestus

### MEV Relay Bids from relays for specific slot. Of these which bids came before slot time

#### Max Bid Over Time
| Relay | Blocks | Avg. <br> Transactions <br> Included | Builders <br> Connected | Median Execution <br> Rewards (ETH) |
| ---: | ---: | ---: | ---: | ---: |
