Fundamentos de Programação

Amdahl's Law

Theoretical limit on parallel speedup: if P% of a task is parallelizable, maximum speedup is 1/(1-P + P/N) for N processors. Limits Sealevel's gains — transactions touching the same account must serialize. Solana mitigates this through account-level locking (maximizing P) and local fee markets (pricing serial contention).

IDamdahls-lawAliasAmdahl's Law

Leitura rápida

Comece pela explicação mais curta e útil antes de aprofundar.

Theoretical limit on parallel speedup: if P% of a task is parallelizable, maximum speedup is 1/(1-P + P/N) for N processors. Limits Sealevel's gains — transactions touching the same account must serialize. Solana mitigates this through account-level locking (maximizing P) and local fee markets (pricing serial contention).

Modelo mental

Use primeiro a analogia curta para raciocinar melhor sobre o termo quando ele aparecer em código, docs ou prompts.

Pense nisso como um bloco de construção que ajuda a ligar uma definição isolada ao sistema maior onde ela vive.

Contexto técnico

Coloque o termo dentro da camada de Solana em que ele vive para raciocinar melhor sobre ele.

Serialização, memória, estruturas de dados e bases de engenharia.

Por que builders ligam para isso

Transforme o termo de vocabulário em algo operacional para produto e engenharia.

Este termo destrava conceitos adjacentes rapidamente, então funciona melhor quando você o trata como um ponto de conexão, não como definição isolada.

Handoff para IA

Handoff para IA

Use este bloco compacto quando quiser dar contexto aterrado para um agente ou assistente sem despejar a página inteira.

Amdahl's Law (amdahls-law)
Categoria: Fundamentos de Programação
Definição: Theoretical limit on parallel speedup: if P% of a task is parallelizable, maximum speedup is 1/(1-P + P/N) for N processors. Limits Sealevel's gains — transactions touching the same account must serialize. Solana mitigates this through account-level locking (maximizing P) and local fee markets (pricing serial contention).
Aliases: Amdahl's Law
Relacionados: Parallel Transaction Execution, Sealevel, Account Locking (Read/Write)
Glossary Copilot

Faça perguntas de Solana com contexto aterrado sem sair do glossário.

Use contexto do glossário, relações entre termos, modelos mentais e builder paths para receber respostas estruturadas em vez de output genérico.

Explicar este código

Opcional: cole código Anchor, Solana ou Rust para o Copilot mapear primitivas de volta para termos do glossário.

Faça uma pergunta aterrada no glossário

Faça uma pergunta aterrada no glossário

O Copilot vai responder usando o termo atual, conceitos relacionados, modelos mentais e o grafo ao redor do glossário.

Grafo conceitual

Veja o termo como parte de uma rede, não como uma definição sem saída.

Esses ramos mostram quais conceitos esse termo toca diretamente e o que existe uma camada além deles.

Ramo

Parallel Transaction Execution

Solana's ability to process multiple transactions simultaneously by analyzing their account access lists and executing non-conflicting transactions in parallel across CPU cores via the Sealevel runtime. Two transactions can run in parallel only if they do not share any writable accounts; transactions sharing a writable account are serialized. This design allows Solana to fully exploit modern multi-core hardware and is a primary contributor to its high throughput.

Ramo

Sealevel

Solana's parallel transaction execution engine. Sealevel can process thousands of transactions simultaneously by analyzing each transaction's declared account inputs—transactions that don't touch the same writable accounts run in parallel across available CPU cores. This account-level parallelism is what enables Solana's high throughput.

Ramo

Account Locking (Read/Write)

The mechanism by which Solana's scheduler reserves access to accounts for the duration of a transaction's execution, granting either shared read locks (multiple transactions can hold simultaneously) or exclusive write locks (only one transaction at a time). Before execution, the runtime inspects every transaction's declared account list and grants or denies locks accordingly, preventing data races without requiring a global mutex. Transactions that cannot acquire all required locks are queued or dropped, making correct account declaration in transaction instructions critical for both correctness and landing probability.

Próximos conceitos para explorar

Continue a cadeia de aprendizado em vez de parar em uma única definição.

Estes são os próximos conceitos que valem abrir se você quiser que este termo faça mais sentido dentro de um workflow real de Solana.

Rede

Parallel Transaction Execution

Solana's ability to process multiple transactions simultaneously by analyzing their account access lists and executing non-conflicting transactions in parallel across CPU cores via the Sealevel runtime. Two transactions can run in parallel only if they do not share any writable accounts; transactions sharing a writable account are serialized. This design allows Solana to fully exploit modern multi-core hardware and is a primary contributor to its high throughput.

Protocolo Base

Sealevel

Solana's parallel transaction execution engine. Sealevel can process thousands of transactions simultaneously by analyzing each transaction's declared account inputs—transactions that don't touch the same writable accounts run in parallel across available CPU cores. This account-level parallelism is what enables Solana's high throughput.

Rede

Account Locking (Read/Write)

The mechanism by which Solana's scheduler reserves access to accounts for the duration of a transaction's execution, granting either shared read locks (multiple transactions can hold simultaneously) or exclusive write locks (only one transaction at a time). Before execution, the runtime inspects every transaction's declared account list and grants or denies locks accordingly, preventing data races without requiring a global mutex. Transactions that cannot acquire all required locks are queued or dropped, making correct account declaration in transaction instructions critical for both correctness and landing probability.

Fundamentos de Programação

API (Application Programming Interface)

A defined interface through which software components communicate. REST APIs use HTTP methods (GET, POST) with JSON payloads. Solana uses JSON-RPC APIs where clients send method calls (getAccountInfo, sendTransaction) to validator nodes. GraphQL APIs (used by some indexers) allow clients to request exactly the data they need in a single query.

Termos relacionados

Siga os conceitos que realmente dão contexto a este termo.

Entradas de glossário só ficam úteis quando estão conectadas. Esses links são o caminho mais curto para ideias adjacentes.

Redeparallel-execution

Parallel Transaction Execution

Solana's ability to process multiple transactions simultaneously by analyzing their account access lists and executing non-conflicting transactions in parallel across CPU cores via the Sealevel runtime. Two transactions can run in parallel only if they do not share any writable accounts; transactions sharing a writable account are serialized. This design allows Solana to fully exploit modern multi-core hardware and is a primary contributor to its high throughput.

Protocolo Basesealevel

Sealevel

Solana's parallel transaction execution engine. Sealevel can process thousands of transactions simultaneously by analyzing each transaction's declared account inputs—transactions that don't touch the same writable accounts run in parallel across available CPU cores. This account-level parallelism is what enables Solana's high throughput.

Redeaccount-locking

Account Locking (Read/Write)

The mechanism by which Solana's scheduler reserves access to accounts for the duration of a transaction's execution, granting either shared read locks (multiple transactions can hold simultaneously) or exclusive write locks (only one transaction at a time). Before execution, the runtime inspects every transaction's declared account list and grants or denies locks accordingly, preventing data races without requiring a global mutex. Transactions that cannot acquire all required locks are queued or dropped, making correct account declaration in transaction instructions critical for both correctness and landing probability.

Mais na categoria

Permaneça na mesma camada e continue construindo contexto.

Essas entradas vivem ao lado do termo atual e ajudam a página a parecer parte de um grafo maior, não um beco sem saída.

Fundamentos de Programação

Rust

A systems programming language emphasizing memory safety, zero-cost abstractions, and concurrency without a garbage collector. Rust uses an ownership model with borrow checking at compile time to prevent data races and null pointer bugs. It is the primary language for Solana program development (via Anchor or native solana-program crate) and the Agave validator client.

Fundamentos de Programação

TypeScript

A statically typed superset of JavaScript that compiles to plain JavaScript. TypeScript adds type annotations, interfaces, generics, and enums to catch errors at compile time. It is the standard language for Solana client-side development—wallet adapters, dApp frontends, test suites, and SDK interactions (web3.js, Anchor client) are typically written in TypeScript.

Fundamentos de Programação

JavaScript

The ubiquitous scripting language for web development, running in browsers and Node.js. JavaScript is dynamically typed and event-driven. Most Solana dApp frontends and scripts use JavaScript/TypeScript with libraries like @solana/web3.js. Node.js enables server-side JS for backend services, indexers, and bot development.

Fundamentos de Programação

Node.js

A JavaScript runtime built on Chrome's V8 engine that enables server-side JavaScript execution. Node.js uses an event-driven, non-blocking I/O model. In the Solana ecosystem, Node.js is used for: running Anchor tests (Mocha/Jest), backend services, transaction bots, indexers, and CLI tools. npm/yarn/pnpm manage JavaScript package dependencies.