Open Ax51 opened 4 days ago
Doesn't behave this way for me, but then I'm on x64, and you're running on an ARM architecture, not to mention Linux vs. macOS...
I have an ARM board I'm planning to get up and running in the next few days, so I can check there, see if anything is different.
Better would be if you could generate a CPU profile. The changes in this branch are all you actually need to generate one: https://github.com/Omnikron13/gh-dash/tree/cpu-profile
go tool pprof cpu.profile
after you close out the profiling build of gh-dash
will open up the interactive tool google ship for probing the profile.
The top10
command might shed some light on what is actually using CPU cycles, or the web
command should generate a nice visualisation of where they're all going in your browser.
Describe the bug A clear and concise description of what the bug is.
Just running the extension consumes about a quarter of the CPU resources. This behaviour is unexpected
To Reproduce Steps to reproduce the behavior:
Activity Monitor app
Activity Monitor
app and check forgh dash
process nameExpected behavior A clear and concise description of what you expected to happen.
Consume less cpu %. For example running
kitty
instance consumes just about0.6%
of cpu. actively runningeslint_d
instance consumes not more than15%
.Screenshots If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):
Update:
Used extension ver.: 4.3.0![image](https://github.com/dlvhdr/gh-dash/assets/80718359/f72ec1f5-758e-41ca-9d98-89050dc11430)