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

[Feature] Reports #20

Open
RiftLurker opened this issue May 17, 2017 · 1 comment
Open

[Feature] Reports #20

RiftLurker opened this issue May 17, 2017 · 1 comment

Comments

@RiftLurker
Copy link
Contributor

RiftLurker commented May 17, 2017

Report is an object that can be created (and optionally saved) from the current profiling data.

It can be consumed by output functions (stream, email, custom).

Long term I can imagine some utility functions to compare Reports.

@gdborton
Copy link
Collaborator

It might be best to standardize the profiler's memory object (I've avoided documenting this as I didn't want it to be public api, but it's pretty stable now) and then create separate repos for generating reports.

The ones that are currently built in can stay, but people can then build their own/depend on the data.

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