Electron CPU usage

[Mykle1]

@djsunrise19 said in Electron CPU usage:

So the question is: Anyone here who doesn’t have those peaks and lags while the transitions with MMv2 and electron?

This topic is only 17 days old, yet it has 5.0k views already. So, obviously there is a lot of interest. My answer likely was lost somewhere above, so:

I do NOT have those peaks and lags

[Mykle1]

@Sean said in Electron CPU usage:

I doubt it goes worse on some late version

With all due respect, I have to disagree. New versions can break existing installations in any software, not just MM. It’s the very reason for many patches. However, we don’t know the reason for this issue, and it may well be that electron isn’t the cause, but some users have had a small measure of improvement with earlier versions.

[loctruong96]

@TiemenMoesker HOLY MOLLY, I am having this exact problem you guys are having. I double checked my hardware and revision. which are
hardware =BCM2835
Revision= a02082
and I DO have this problem, it seems nothing you guys tried work except downgrade , so I’m going to ask arrow to send me a replacement since i actually ordered BCM2837 not BCM2835. Let’s hope it work out! (mean while I will try the downgrade option, seemed to improve performance drastically for others)

[Mykle1]

@loctruong96 said in Electron CPU usage:

(mean while I will try the downgrade option, seemed to improve performance drastically for others)

Please keep us posted

[loctruong96]

OK, I can here by confirm that using MM 2.1.0 + Electron 1.4.15 improved performance massively. Each new transition now only uses 10-13% of CPU power (and very, very smooth). Even better than earlier report of 40%. For the specs of my pi 3 b
hardware = BCM2835
Revision = a02082
micro sd card - 16gb - class 4 (that’s right, only 4)
mouse + keyboard currently plugged in - no lag
OS = RASPBIAN STRETCH WITH DESKTOP
Thank you so much @Mykle1 for sharing your finding. Otherwise, I would be still trying to narrow down a potential work around.

For those who not sure how to do this:

1. Create a fresh install of RASPBIAN STRETCH WITH DESKTOP, connect to wifi, then run sudo apt-get update.
2. sudo apt-get install npm
3. sudo npm install electron@1.4.15 -g
4. WAIT PATIENTLY FOR ELECTRON TO LOAD IN THE BACKGROUND
5. a new line appear indicate electron has finished installing
6. Go to your download folder, exact Magic Mirror 2.1.0
7. Go to the newly exacted forlder, open another folder named config
8. Change the file name Config.js.example to Config.js inside the config folder
9. open terminal , cd Download/, cd MagicMirror-2.1.0, (OR whatever your location for the Magic Mirror 2.1.0 package is), npm install && npm start
   9.5 If encounter error “404”, try “npm install npm@latest -g” (NOTE: some users experienced issues since they do not have the latest npm as global variable) @Reotch2 @EventHorizon
10. DONE!

Hopefully I will be able to return my pi 3 for a better hardware version to use with the latest Magic Mirror package but here is an acceptable work around for the time being.

[Mykle1]

@loctruong96 said in Electron CPU usage:

Thank you so much @Mykle1 for sharing your finding.

You are most welcome. :^)

I would like to give credit to everyone that is participating in this topic. By putting our heads together we’ve eliminated some possibilities but we haven’t pinpointed the problem, yet. We have narrowed it down a bit, though, and this workaround is helping some people. I’m glad you’re one of them.

[EventHorizon]

Just a quick post in an attempt to re-create the above steps. I get to the part where I have to type “npm install && npm start” and I get an error 404 ‘Not Found’. ‘types/node’ is not in the npm registry. ‘It was specified as a dependency of ‘electron’’

Any idea what I’m doing wrong?

Thanks.

[strawberry 3.141]

@EventHorizon it should be @types/node

[EventHorizon]

@strawberry-3.141 thank you for the quick reply. Just to confirm: where am I entering @types/node. Sorry for being a noob at this. Thanks for your help!

EDIT: I got the node/type to work by updating using sudo npm install npm@latest -g

Now when I run sudo npm install in the magic mirror folder I get an error code LIFECYCLE. errno 1. “electron@1.7.6” postinstall ‘node install.js’.

‘failed at the electron@1.7.6 postinstall script’.

Any ideas?

EDIT2: used sudo npm install -g electron --unsafe-perm=true.

This seemed to work. I will monitor performance and let you all know.

EDIT3:

Been monitoring it for an hour or so now. CPU temp has not gone over 50. While before it was around a constant 60 - 65.
Compliments and Newsfeed animations are SUPER SMOOTH.

I can confirm that using MM 2.1.0 with Electron 1.4.15 has insanely improved performance! Thanks to everyone in this thread and to @Mykle1 for pointing this thread out for me.

I just have ONE final question guys. I used my custom.css file from my newer build and all was fine after I removed the ‘everyday’ segment of the code from the compliments module. HOWEVER…I notice in the background (If i tab to terminal) This message pops up:

“Fatal: not a git repository (or any of the parent directories): .git”

However, it does not seem to affect the mirror? Or not in any way I can see? Is there any way I can pinpoint how this message is being generated? Like I said, it does not appear to affect any of my modules.

Any help would be greatly appreciated.

Cheers all!

[Mykle1]

@EventHorizon said in Electron CPU usage:

I can confirm that using MM 2.1.0 with Electron 1.4.15 has insanely improved performance! Thanks to everyone in this thread and to @Mykle1 for pointing this thread out for me.

If you read this entire thread then you know that I’ve been at this for three weeks. It started as a question from a single user and grew quickly and substantially. 148 posts and 6.0k views later showed there was/is an issue affecting many users, yourself included. I’m glad this workaround has helped you. Enjoy!

“Fatal: not a git repository (or any of the parent directories): .git”

I get these, too, when I do a manual installation of a module, or the MM software itself. What type of installation did you do?

In any event, it does not affect the operation of the MM software. Perhaps someone will give us a more detailed description of why it appears.