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

This software eats an absurd amount of cpu cycles!!! #12

Open
COLABORATI opened this issue Dec 8, 2017 · 1 comment
Open

This software eats an absurd amount of cpu cycles!!! #12

COLABORATI opened this issue Dec 8, 2017 · 1 comment

Comments

@COLABORATI
Copy link

I really like speedometer - unfortunately it definitely is not an acceptable tool for measuring a potentially already heavily stressed system, it eats too many cpu cycles! On a decent Linux laptop with a fast Core i7 speedometer is the most cpu intensive process with around 7-10% CPU usage visible in htop - this is insane! Even Chromium browser does not spend so much with many tabs open!

This is by far the most absurd case of a system measurement tool that stresses the system itself that I have ever seen - a good candidate for an "absurd software award" that should exist.

@wardi
Copy link
Owner

wardi commented Dec 8, 2017

Would you provide some more details? I see about 1% CPU on an i5 laptop running Linux. If I monitor a bunch of interfaces and make the font small and window really large I can get that up to about 6%. While that's not great I don't think would be eligible for any sort of award :-)

If you like speedometer and want to see it perform better, please attach a python profile report from running urwid on your system so we can see what's contributing the most to CPU usage.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants