Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

wip: refactor payload processing #14589

Draft
wants to merge 12 commits into
base: main
Choose a base branch
from
Draft

wip: refactor payload processing #14589

wants to merge 12 commits into from

Conversation

mattsse
Copy link
Collaborator

@mattsse mattsse commented Feb 19, 2025

No description provided.

///
/// # Transaction prewarming task
///
/// Responsible for feeding state updates to the state root task.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

also warming revm caches, right?

///
/// ## State root task
///
/// Responsible for preparing sparse trie messages for the sparse trie task.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

i see, so state root task will only spawn multiproofs and send results back to PayloadProcessor, but PayloadProcessor itself will send the state update + multiproof to sparse trie task?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

send results back to PayloadProcessor

send back to itself. PayloadProcessor is just some helper that spawns these 3 tasks

/// - externally cancelled (e.g. sequential block execution is complete)
/// - all transaction have been processed
///
/// ## State root task
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

let's rename this to multiproof task?

@emhane emhane added C-debt A clean up/refactor of existing code A-engine Related to the engine implementation C-perf A change motivated by improving speed, memory usage or disk footprint labels Feb 21, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-engine Related to the engine implementation C-debt A clean up/refactor of existing code C-perf A change motivated by improving speed, memory usage or disk footprint
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants