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

[Merged by Bors] - Increase logging channel capacity #1570

Closed

Conversation

realbigsean
Copy link
Member

Issue Addressed

#1464

Proposed Changes

Increase the slog-async log channel size from the default of 128 to 2048 to reduce the number of dropped logs.

Additional Info

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.

Looks good to me, would be interested to see if @paulhauner has any thoughts

Copy link
Member

@paulhauner paulhauner left a comment

Choose a reason for hiding this comment

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

Looks good to me. From the size of the overflows I've seen 2048 should easily cover it.

…ease-logging-channel-capacity

# Conflicts:
#	Cargo.lock
@AgeManning
Copy link
Member

bors r+

bors bot pushed a commit that referenced this pull request Aug 31, 2020
## Issue Addressed

#1464

## Proposed Changes

Increase the slog-async log channel size from the default of 128 to 2048 to reduce the number of dropped logs. 

## Additional Info
@bors bors bot changed the title Increase logging channel capacity [Merged by Bors] - Increase logging channel capacity Aug 31, 2020
@bors bors bot closed this Aug 31, 2020
darcys22 pushed a commit to darcys22/lighthouse that referenced this pull request Sep 5, 2020
## Issue Addressed

sigp#1464

## Proposed Changes

Increase the slog-async log channel size from the default of 128 to 2048 to reduce the number of dropped logs. 

## Additional Info
@realbigsean realbigsean deleted the increase-logging-channel-capacity branch November 21, 2023 16:14
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants