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

Hot-fix v4.0.2-rc.0 #4181

Closed
wants to merge 3 commits into from
Closed

Hot-fix v4.0.2-rc.0 #4181

wants to merge 3 commits into from

Conversation

paulhauner
Copy link
Member

Issue Addressed

NA

Proposed Changes

Avoids clones and state-skips of the head state when an exit is verified across a skip slot.

Additional Info

NA

@paulhauner paulhauner added ready-for-review The code is ready for review do-not-merge labels Apr 12, 2023
@paulhauner paulhauner changed the base branch from stable to unstable April 12, 2023 23:30
Copy link
Member

@michaelsproul michaelsproul left a comment

Choose a reason for hiding this comment

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

I've reviewed this

@TennisBowling
Copy link

with maxperf this reduces spikes from all cores ~70%+ to ~20%+ on a ryzen 9 5950x so might still be hitting hard for pi 4's

@paulhauner paulhauner added do-not-merge and removed ready-for-review The code is ready for review labels Apr 13, 2023
@paulhauner
Copy link
Member Author

paulhauner commented Apr 13, 2023

I don't think we should merge this branch into unstable since it contains the version bump commits.

Rather, I think we should keep this branch around (i.e., not deleted) so it can be pulled by users and we should make another PR to merge into unstable.

@paulhauner paulhauner changed the title Use head state for exit verification v4.0.2-rc.0 Apr 13, 2023
@paulhauner paulhauner changed the title v4.0.2-rc.0 Hot-fix v4.0.2-rc.0 Apr 13, 2023
bors bot pushed a commit that referenced this pull request Apr 14, 2023
## Issue Addressed

NA

## Proposed Changes

Similar to #4181 but without the version bump and a more nuanced fix.

Patches the high CPU usage seen after the Capella fork which was caused by processing exits when there are skip slots.

## Additional Info

~~This is an imperfect solution that will cause us to drop some exits at the fork boundary. This is tracked at #4184.~~
@dom-nie
Copy link

dom-nie commented Apr 19, 2023

@paulhauner @michaelsproul Will there be a release without the -rc suffix?

@michaelsproul
Copy link
Member

@dom-nie Yeah, v4.1.0 tomorrow: #4191 (all being well with testing overnight)

@paulhauner
Copy link
Member Author

paulhauner commented Apr 26, 2023

Please expect this branch to be deleted in the near future.

All users should prefer the latest release (v4.1.0 at the time of writing).

@paulhauner
Copy link
Member Author

I'm closing this PR but leaving the branch around for the time being.

All users should prefer the latest release (v4.1.0 at the time of writing).

@paulhauner paulhauner closed this Apr 27, 2023
ghost pushed a commit to oone-world/lighthouse that referenced this pull request Jul 13, 2023
## Issue Addressed

NA

## Proposed Changes

Similar to sigp#4181 but without the version bump and a more nuanced fix.

Patches the high CPU usage seen after the Capella fork which was caused by processing exits when there are skip slots.

## Additional Info

~~This is an imperfect solution that will cause us to drop some exits at the fork boundary. This is tracked at sigp#4184.~~
Woodpile37 pushed a commit to Woodpile37/lighthouse that referenced this pull request Jan 6, 2024
## Issue Addressed

NA

## Proposed Changes

Similar to sigp#4181 but without the version bump and a more nuanced fix.

Patches the high CPU usage seen after the Capella fork which was caused by processing exits when there are skip slots.

## Additional Info

~~This is an imperfect solution that will cause us to drop some exits at the fork boundary. This is tracked at sigp#4184.~~
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants