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.

Sign up for GitHub

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

Jump to bottom

Take a look at detecting memory changes after each op in the optree #4

Open
wolfsage opened this issue Sep 23, 2011 · 0 comments
Open

Take a look at detecting memory changes after each op in the optree #4

wolfsage opened this issue Sep 23, 2011 · 0 comments

Comments

@wolfsage
Copy link
Owner

If possible, it would be awesome if DMTL could detect memory changes after calls to ops, and Deparse and give an idea of what code caused the increase.

https://metacpan.org/module/optimizer may prove useful.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@wolfsage