hovancik/stretchly

[Bug]: Stretchly on M1 seems to be consuming too much energy

Open

#1278 opened on Mar 3, 2023

View on GitHub
 (5 comments) (1 reaction) (0 assignees)JavaScript (3,892 stars) (410 forks)batch import
help wanted

Description

Version

  • I'm using version 1.13.1

Known issues

  • I've checked Known issues

Existing issues

  • I've checked Existing issues

What operating system are you using?

macOS

Operating System Version

Ventura 13.2.1

Reproduction steps

  1. Open Stretchly
  2. Open Activity Monitor
  3. Check energy consumption

Expected Behavior

I would expect a fairly passive app like Stretchly to be in the low consuming spectrum. I am currently using Time Out, not because I like the experience better, but because consumption seems to be approximately 5x lower.

Thanks for the hard work!

Actual Behavior

Apple's algorithm for estimating energy consumption is closed source (sucks), but there seems to be a correlation with the amount of threads and idle wake ups.

Relevant log output

No response

Preferences

No response

Additional information

No response

Code of Conduct

  • I agree to follow this project's Code of Conduct

Contributor guide

Tech stack
electronjavascriptnodejs
Domain
desktopperformance
Issue type
performance
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
3-5 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
mostly clear
Prerequisites
Basic knowledge of ElectronmacOS energy profiling tools (Instruments)
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
35
Research direction
Investigate energy usage of the Electron app on M1 Mac using Activity Monitor and Xcode Instruments. Look for excessive timers, high CPU usage, or frequent idle wake ups in the main and renderer processes. Compare with similar break time apps like Time Out. Potential areas to explore: the use of setInterval for break timers, rendering of notifications, or unnecessary background activity. Files to examine include the main process entry point and timer related modules.