Skip to content

Add new giga executor to sei with config #2668

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.

Sign up for GitHub

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

Jump to bottom
Open
stevenlanders wants to merge 5 commits into
base: pd/evmc-vm
Choose a base branch
from
Open

Add new giga executor to sei with config #2668

stevenlanders wants to merge 5 commits into from

Conversation

@stevenlanders
Copy link
Contributor

@stevenlanders stevenlanders commented Jan 6, 2026 •
edited
Loading

Describe your changes and provide context

  • adds new config for process block
  • instruments scripts to use new executor if flag is passed
  • adds

Testing performed to validate your change

# run giga with OCC
GIGA_EXECUTOR=true GIGA_OCC=true ./scripts/benchmark.sh

# run giga without OCC (direct sequential execution with no scheduler)
GIGA_EXECUTOR=true GIGA_OCC=false ./scripts/benchmark.sh

# run non-giga 
GIGA_EXECUTOR=false ./scripts/benchmark.sh

@github-actions
Copy link

github-actions bot commented Jan 6, 2026 •
edited
Loading

The latest Buf updates on your PR. Results from workflow Buf / buf (pull_request).

BuildFormatLintBreakingUpdated (UTC)
✅ passed✅ passed✅ passed✅ passedJan 8, 2026, 9:46 PM

@stevenlanders
Add OCC to giga (#2677)
a835d23 
## Describe your changes and provide context
- wraps giga with occ 
- leaves sequential giga in place 

## Testing performed to validate your change
- more benchmarking via benchmark.sh
@stevenlanders stevenlanders changed the title Adjust flow to use new executor Add new giga executor to sei with config Jan 8, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

non-app-hash-breaking

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@stevenlanders