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

Breakdown invocation counts are misleading for operations called in a loop #45

Open
geoffxy opened this issue Feb 9, 2020 · 0 comments
Assignees
Labels
bug Something isn't working server This is primarily related to the server

Comments

@geoffxy
Copy link
Member

geoffxy commented Feb 9, 2020

When we call an operation in a loop, our hierarchical breakdown builder will group all invocations together into a single breakdown node. We calculate the run time and memory consumption correctly, but our current implementation results in only a single instance of the operation being reported. This can be misleading to the end user.

@geoffxy geoffxy added bug Something isn't working server This is primarily related to the server labels Feb 9, 2020
@geoffxy geoffxy self-assigned this Feb 9, 2020
@geoffxy geoffxy modified the milestones: v0.3.0, v0.4.0 Feb 9, 2020
@geoffxy geoffxy removed this from the v0.4.0 milestone Feb 21, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working server This is primarily related to the server
Projects
None yet
Development

No branches or pull requests

1 participant