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

CPU Usage When Idle #400

Open
Enverex opened this Issue Dec 21, 2017 · 6 comments

Comments

Projects
None yet
2 participants
@Enverex
Contributor

Enverex commented Dec 21, 2017

CPU usage when playing videos or switching content during the screen-saver is understandable, but it appears that AM is still "active" even after hitting the "screen_saver_timeout". The screen goes black and you'd assume that everything has "stopped" but I'm still seeing 4-6% CPU usage on an i7 machine.

Is it possible to make AM actually properly sleep and stop using CPU time when it should be in this standby type mode?

@oomek

This comment has been minimized.

Show comment
Hide comment
@oomek

oomek Jan 8, 2018

Collaborator

Why won’t you trigger the proper sleep mode instead of just blanking the screen?

Collaborator

oomek commented Jan 8, 2018

Why won’t you trigger the proper sleep mode instead of just blanking the screen?

@oomek

This comment has been minimized.

Show comment
Hide comment
@oomek

oomek Jan 8, 2018

Collaborator

Add this as a command in screensaver settings

rundll32.exe powrprof.dll,SetSuspendState 0,1,0

Collaborator

oomek commented Jan 8, 2018

Add this as a command in screensaver settings

rundll32.exe powrprof.dll,SetSuspendState 0,1,0

@Enverex

This comment has been minimized.

Show comment
Hide comment
@Enverex

Enverex Jan 8, 2018

Contributor

Why won’t you trigger the proper sleep mode instead of just blanking the screen?

Are you talking to me or mickelson? If me, then it's because I still need the machine accessible over the network.

Add this as a command in screensaver settings

Not relevant on Linux, and again, that puts the entire machine in suspend which isn't what we're discussing here.

This bug is about AttractMode still using a decent amount of CPU time despite being idle (with no content playing).

Contributor

Enverex commented Jan 8, 2018

Why won’t you trigger the proper sleep mode instead of just blanking the screen?

Are you talking to me or mickelson? If me, then it's because I still need the machine accessible over the network.

Add this as a command in screensaver settings

Not relevant on Linux, and again, that puts the entire machine in suspend which isn't what we're discussing here.

This bug is about AttractMode still using a decent amount of CPU time despite being idle (with no content playing).

@oomek

This comment has been minimized.

Show comment
Hide comment
@oomek

oomek Jan 8, 2018

Collaborator

Ok, fair enough. Didn’t know you are on linux.

Collaborator

oomek commented Jan 8, 2018

Ok, fair enough. Didn’t know you are on linux.

mickelson added a commit that referenced this issue Jan 9, 2018

@Enverex

This comment has been minimized.

Show comment
Hide comment
@Enverex

Enverex Jan 18, 2018

Contributor

I'm now seeing usage between 0 and 2%. Much better but not perfect (not sure what's causing the 2% spike roughly 50% of the time). Is it simply because it's sat in that 15ms delay game loop at that point?

Contributor

Enverex commented Jan 18, 2018

I'm now seeing usage between 0 and 2%. Much better but not perfect (not sure what's causing the 2% spike roughly 50% of the time). Is it simply because it's sat in that 15ms delay game loop at that point?

@Enverex

This comment has been minimized.

Show comment
Hide comment
@Enverex

Enverex Jan 21, 2018

Contributor

Found an interesting bug tied to this. If my screen is off and AttractMode goes to "sleep", it eats 100% CPU (100% of a single core) whilst not doing anything. Waking it back up causes it to go back to ~25% CPU when showing a video in the games list.

Contributor

Enverex commented Jan 21, 2018

Found an interesting bug tied to this. If my screen is off and AttractMode goes to "sleep", it eats 100% CPU (100% of a single core) whilst not doing anything. Waking it back up causes it to go back to ~25% CPU when showing a video in the games list.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment