hovancik/stretchly

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

Open

#1,278 建立於 2023年3月3日

在 GitHub 查看
 (5 留言) (1 反應) (0 負責人)JavaScript (3,892 star) (410 fork)batch import
help wanted

描述

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

貢獻者指南

技術棧
electronjavascriptnodejs
領域
desktopperformance
議題類型
performance
難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。
3
預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。
3-5 days
活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。
stale
清晰度議題是否清楚說明預期改動、驗收標準和下一步。
mostly clear
前置要求
Basic knowledge of ElectronmacOS energy profiling tools (Instruments)
新手友善度1-100 的估計分數，表示該議題對首次貢獻者的友善程度。
35
研究方向
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.