golemfactory / golem-electron

Graphical user interface for Golem Project

Home Page:https://golem.network

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Excessive CPU usage after running Electron for longer period

cryptobench opened this issue · comments

Description

After Golem has been running for 10-20 hours hours, i've been noticing that it suddenly uses a lot of CPU usage. It can go on for around 5 hours I would assume and then the CPU usage is back to normal.

Electron version:
Not sure - the one that comes with default install.sh script for Ubuntu version 0.19.1
Golem Version:
0.19.1

Golem-Messages version (leave empty if unsure):

OS [e.g. Windows 10 Pro]:
Ubuntu 18.04

Branch (if launched from source):

Mainnet/Testnet:
Mainnet

Description of the issue:
Sudden CPU usage spike with no explanation for it whatsoever. No tasks running as I checked the field with I only wanna act as a requestor

Actual result:
Spike in CPU usage for longer period of time.

Screenshots:
image

Steps To Reproduce

  1. Launch Golem Mainnet
  2. Check act as requestor only.
  3. Wait

Expected behavior

Sudden spike in CPU usage for a longer period of time.

Logs and any additional context

Logs only shows connecting to peer n , in that time period.

Proposed Solution?

Hello @cryptobench ! Could you tell me which screen/tab/section was displaying in the app while waiting? Was it "Network", "Tasks" or "Settings" ?

Hey, @mdtanrikulu ! The issue just appeared again. New screenshots
image
image

@cryptobench Thank you! I will take care about it.

Thanks for looking into it. I would love to provide more info, but nothing really stands out to me what could cause it. Restarting Golem always resolves it.

This commit (7add06a) solved part of the issue.
Unnecessary updates are removed and/or restricted. The change is already landed with Golem v0.19.2.
So please let me know if you have a chance to observe it.

Nice! I honestly haven't noticed this issue for some time so that most likely fixed the issue. Thanks for looking into it! @mdtanrikulu