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

Enable use of counter-trees for performance sensitive instrumentation #17

Open
hjdivad opened this issue Aug 16, 2016 · 1 comment
Open

Comments

@hjdivad
Copy link
Collaborator

hjdivad commented Aug 16, 2016

One idea of Kris's was to support counter-trees. These are just like nodes but without time, so they do not even pay the cost of performance.now.

So we'd have nodes with some children that were nodes, and a separate graph of counters with no time information.

@runspired
Copy link
Collaborator

Would not be difficult to achieve this, there can even be a marginal amount of time interleaving. We'd just need heimdall.segmentCounters() to push OP_SEGMENT into the events array with the current counter cache.

@runspired runspired changed the title maybe support stacks of counters Enable use of counter-trees for performance sensitive instrumentation Feb 27, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants