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

Observability: Track bytes per transaction #2023

Open
joshua-spacetime opened this issue Nov 27, 2024 · 1 comment
Open

Observability: Track bytes per transaction #2023

joshua-spacetime opened this issue Nov 27, 2024 · 1 comment
Assignees

Comments

@joshua-spacetime
Copy link
Collaborator

Motivation: Reducer timing spans do not account for all work done in the transaction. In particular they do not take into account the final step of updating the committed state. Tracking bytes modified/written will provide more clarity when there is a discrepancy between timing spans and reducer duration metrics.

@joshua-spacetime joshua-spacetime self-assigned this Nov 27, 2024
@cloutiertyler
Copy link
Contributor

The energy accounting may need a similar metric, which will be calculated based on work in another ticket.

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

No branches or pull requests

2 participants