Display vote/nonvote txs and add goroutine scheduling info in trace#202
Merged
7layermagik merged 2 commits intodevfrom Feb 6, 2026
Merged
Display vote/nonvote txs and add goroutine scheduling info in trace#2027layermagik merged 2 commits intodevfrom
7layermagik merged 2 commits intodevfrom
Conversation
7layermagik
approved these changes
Feb 6, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Seeing that a large number of transactions are votes, I decided to break them out into their own category in the trace. Then I saw that most votes are processed in <60 microseconds, but some take 1ms or more. I added goroutine scheduling information and it seems that the vote transactions that are slow are trying to acquire a lock, getting put into the WAITING state by the Go scheduler, and then remaining in RUNNABLE for a long time, before continuing to execute.