Solana Compute Units Explained

Compute units (CUs) are Solana's measure of computational work. Every instruction executed during a transaction consumes a certain number of compute units, and understanding this system is key to managing transaction fees effectively. Think of compute units as the 'fuel' that powers your transaction's execution on the Solana virtual machine.

Each transaction has a compute budget — a maximum number of CUs it is allowed to consume. By default, the limit is 200,000 CUs per instruction and up to 1,400,000 CUs per transaction. Simple SOL transfers typically use only 300–500 CUs, while complex DeFi operations involving multiple program invocations can consume 100,000–800,000 CUs. If a transaction exceeds its compute budget, it fails and the base fee is still charged.

Setting your compute unit limit too high wastes money on priority fees. Setting it too low causes transaction failures. Simulation before submission is the professional approach.

The relationship between compute units and fees is direct: priority fee = ceil(compute_unit_price × compute_unit_limit ÷ 1,000,000) lamports. If you set a compute_unit_price of 1,000 micro-lamports and a limit of 200,000 CUs, your priority fee is 200 lamports (about $0.00000003 at $150 SOL). Multiplying this across millions of transactions shows why CU optimization matters at scale.

Developers can request a custom compute budget using the ComputeBudgetProgram. Call setComputeUnitLimit() to specify the maximum CUs your transaction may use, and setComputeUnitPrice() to set the micro-lamport price per CU. These instructions should be included as the first instructions in your transaction for proper scheduling. The Solana documentation provides worked examples for all major SDKs including TypeScript, Rust, and Python.