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

Energy consumption in debug mode might be different #345

Open
aion-shidokht opened this issue Jan 25, 2019 · 1 comment
Open

Energy consumption in debug mode might be different #345

aion-shidokht opened this issue Jan 25, 2019 · 1 comment

Comments

@aion-shidokht
Copy link
Contributor

In debug mode, line numbers are preserved which leads to additional labels being created. Thus, the code blocks detected are smaller. In certain scenarios where a method's logic is not fully executed, debug mode's energy consumption is lower than the normal mode. Depending on where a method's execution is stopped and an exception is thrown, the energy consumed is different in debug mode. With the current implementation the user is charged only for what is executed.
@fulldecent
Copy link
Contributor

Is it possible to please provide a minimal test case?

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
2 participants
@fulldecent @aion-shidokht