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

Publicly monitor power-usage progress #22074

Closed
Kroc opened this issue Mar 6, 2017 · 1 comment
Closed

Publicly monitor power-usage progress #22074

Kroc opened this issue Mar 6, 2017 · 1 comment
Labels
feature-request Request for new features or functionality *out-of-scope Posted issue is not in scope of VS Code perf workbench-diagnostics General VS Code built-in diagnostic issues

Comments

@Kroc
Copy link

Kroc commented Mar 6, 2017

VSCode is obscenely inefficient with battery-power. With Notepad++ I can get 4 to 5 hours. With VSCode I'd be lucky to get 2.5 hours.

This is not a duplicate of #16963 (uses significant energy); I would like the VSCode team publicly track power-usage in the same fashion Mozilla track browser speed with https://arewefastyet.com

If this is not charted and publicly displayed I feel that power-usage will forever be an after-thought and serious regressions could occur unless an eye is being kept on it for every release.

Thanks very much BTW for the great editor.

@bpasero bpasero added feature-request Request for new features or functionality workbench labels Mar 6, 2017
@bpasero bpasero removed their assignment Mar 6, 2017
@bpasero bpasero added the perf label Mar 6, 2017
@bpasero bpasero added workbench-diagnostics General VS Code built-in diagnostic issues and removed workbench labels Nov 16, 2017
@mjbvz mjbvz added the *out-of-scope Posted issue is not in scope of VS Code label May 17, 2018
@vscodebot
Copy link

vscodebot bot commented May 17, 2018

This issue is being closed to keep the number of issues in our inbox on a manageable level, we are closing issues that have been on the backlog for a long time but have not gained traction: We look at the number of votes the issue has received and the number of duplicate issues filed. If you disagree and feel that this issue is crucial: We are happy to listen and to reconsider.

If you wonder what we are up to, please see our roadmap and issue reporting guidelines.

Thanks for your understanding and happy coding!

@vscodebot vscodebot bot closed this as completed May 17, 2018
@vscodebot vscodebot bot locked and limited conversation to collaborators Jul 1, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
feature-request Request for new features or functionality *out-of-scope Posted issue is not in scope of VS Code perf workbench-diagnostics General VS Code built-in diagnostic issues
Projects
None yet
Development

No branches or pull requests

3 participants