COG uses 50% cpu

[ghost]

As discussed in the thread on Google+ launching COG drives CPU usage up from 4% to about 60%

[beaufortfrancois]

Thank you for submitting this.
Will see what I can do to fix that.

For reference, here are some additional notes from Google+:

Additional notes: on my CB memory usage didn't seem excessive. Screenshots in bug report show about 0.4gb if memory serves. Also on my windows 8.1 i5-3210 with b6 GB ram, CPU went from 1% to 16%, but its a quad-core so maybe that's why it didn't go up as much as on the CB.
https://plus.google.com/+MichaelMcNeil/posts/BRs5ZWi6TVB

[ghost]

Sure, while your at it, it might be an idea to make the window scrollable. On all my devices it opens up without a scrollbar on the side, so the info at the bottom is cut off, depending on the screen res, I guess. This occurs even at full-screen. This capture is from my Linux machine, but behaviour is same on my Windows 8.1 and Chromebook. On my Chromebook, I think even more is truncated at the bottom.

[beaufortfrancois]

We are already tracking this weird behaviour at #2

[alfonsojon]

This issue is especially noticeable on the ARM-based Chromebooks.

[beaufortfrancois]

I've tracked this down and it looks the CSS Animation was causing the issue. I've patched this and updated the Web Store App at https://chrome.google.com/webstore/detail/difcjdggkffcfgcfconafogflmmaadco.

Please let me know if it's better for you too.

[alfonsojon]

Still using a good amount of CPU on my Samsung ARM Chromebook (GPU Process).

[jgw96]

Same problem on my Acer c720 chromebook; cog uses about 1.85 gigs of memory. Could the chrome system api's somehow hog memory?

[vivekannan]

Not sure if these changes would help with the CPU usage but we could try,

1. Use chrome API event listeners for storage and display.
2. Should query for the selectors only once during init and not during each update call.

Would love to make a pull. Holler if needed!

[beaufortfrancois]

I've tried removing updateDisplays and updateStorage completely and it doesn't change anything as far as I can tell.
What we could do is to lower down the interval (500ms) but it makes the CPU usage UI kinda bland ;(

[vivekannan]

Yeah, i tried rewriting it so that the document.querySelector is run only once, didn't make any difference either. :(

…

On Mon, Mar 6, 2017 at 1:55 PM, François Beaufort ***@***.***> wrote: I've removed updateDisplays and updateStorage completely and it doesn't change anything as far as I can tell. What we could do is to lower down the interval (500ms) but it makes the CPU usage UI kinda bland ;( — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#5 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AHkl-lolLlq2cvuqtQxih5wFb4LevSdgks5ri8MUgaJpZM4CaizS> .