Posted October 12, 2019
Is this normal? Galaxy is using nearly 30% of an i7-9700K while just sitting around doing nothing. Feels excessive.
No posts in this topic were marked as the solution yet. If you can help, add your reply
Serin9X
New User
Registered: Jun 2013
From United States
Demitrix2k
I like New Vegas
Registered: Dec 2016
From Norway
Posted October 12, 2019
You know, 30% is no doubt not part of the plan, any chance you are using an unofficial plugin?
GenlyAi
New User
Registered: Jun 2011
From Brazil
Posted October 12, 2019
Not for me... mine is completely negligible actually, on ai70-6700. I'm using any possible integration / plugin except XBox Live and Playstation.
Does that happen all the time? Intermittently? in peaks? Have you tried 'disconnecting' some 'integrations' to see if it makes a difference?
Does that happen all the time? Intermittently? in peaks? Have you tried 'disconnecting' some 'integrations' to see if it makes a difference?
Demitrix2k
I like New Vegas
Registered: Dec 2016
From Norway
Posted October 12, 2019
Im gonna reach and guess you have an emulator plugin thats outdated made by https://github.com/JTNDev
I tried his gamecube integration and found problems with the way his timetracker functioned, he updated* it but i have yet to test since i just use methods that dont require plugins for emulators
https://github.com/JTNDev/galaxy-integration-gc/issues/6
I tried his gamecube integration and found problems with the way his timetracker functioned, he updated* it but i have yet to test since i just use methods that dont require plugins for emulators
https://github.com/JTNDev/galaxy-integration-gc/issues/6
Post edited October 12, 2019 by Demitrix2k
ussnorway
New User
Registered: Jun 2011
From Australia
Posted October 13, 2019
its normal at boot time... are you perhaps allowing Galaxy to boot at Windows start?
once everything is loaded up... which will have to wait until your network is fully working and Windows updates will block that at system boot the Galaxy should idel around 3% -5% cpu
once everything is loaded up... which will have to wait until your network is fully working and Windows updates will block that at system boot the Galaxy should idel around 3% -5% cpu
TT_TT_TT_TT
Notanew user -.-
Registered: May 2011
From Germany
Posted October 13, 2019
With a standard galaxy 2.0 without any custom plugins installed its definitely not normal.
My Galaxy uses about 0,2% CPU on an I7 7700K while being idle and i have about 1000 games in it
My Galaxy uses about 0,2% CPU on an I7 7700K while being idle and i have about 1000 games in it
GenlyAi
New User
Registered: Jun 2011
From Brazil
Serin9X
New User
Registered: Jun 2013
From United States
Posted October 26, 2019
Ok so I've been monitoring it over the last few days and I've come to the following conclusions:
1: I'm not using any plugins that didn't come with the client. I have connections active to GOG, Epic, Origin, PSN, Steam, and Uplay. All these plugins came with the stock client download.
2: The Steam plugin in particular is CPU heavy. This means that any time the Steam plugin is working (not crashed which does happen quite a bit) it's drawing something like 10% CPU all by itself. I narrowed this down by tracking the python processes the Galaxy client is using to operate its integrations. All of them spike at load but most of them calm back down after a minute or two. Steam not so much.
3: I don't know what precisely caused the 30% CPU draws I was seeing originally. Probably a combination of factors, but I wasn't tracking anything in particular at the time so I can't know for certain. I do know that the CPU usage while the client is active is quite high, and much higher when another client is active at the same time, which for a launcher that launches launchers, this is not super unreasonable.
I want to also mention on the subject of the Steam plugin, my Steam library is enormous (almost 800 games). I wouldn't consider it unreasonable for a library of that size to take some time to scrape through. Depending on how often Galaxy is doing that, I could easily see it causing high CPU draws.
1: I'm not using any plugins that didn't come with the client. I have connections active to GOG, Epic, Origin, PSN, Steam, and Uplay. All these plugins came with the stock client download.
2: The Steam plugin in particular is CPU heavy. This means that any time the Steam plugin is working (not crashed which does happen quite a bit) it's drawing something like 10% CPU all by itself. I narrowed this down by tracking the python processes the Galaxy client is using to operate its integrations. All of them spike at load but most of them calm back down after a minute or two. Steam not so much.
3: I don't know what precisely caused the 30% CPU draws I was seeing originally. Probably a combination of factors, but I wasn't tracking anything in particular at the time so I can't know for certain. I do know that the CPU usage while the client is active is quite high, and much higher when another client is active at the same time, which for a launcher that launches launchers, this is not super unreasonable.
I want to also mention on the subject of the Steam plugin, my Steam library is enormous (almost 800 games). I wouldn't consider it unreasonable for a library of that size to take some time to scrape through. Depending on how often Galaxy is doing that, I could easily see it causing high CPU draws.
GenlyAi
New User
Registered: Jun 2011
From Brazil
Posted October 29, 2019
1: I'm not using any plugins that didn't come with the client. I have connections active to GOG, Epic, Origin, PSN, Steam, and Uplay. All these plugins came with the stock client download.
2: The Steam plugin in particular is CPU heavy. This means that any time the Steam plugin is working (not crashed which does happen quite a bit) it's drawing something like 10% CPU all by itself. I narrowed this down by tracking the python processes the Galaxy client is using to operate its integrations. All of them spike at load but most of them calm back down after a minute or two. Steam not so much.
3: I don't know what precisely caused the 30% CPU draws I was seeing originally. Probably a combination of factors, but I wasn't tracking anything in particular at the time so I can't know for certain. I do know that the CPU usage while the client is active is quite high, and much higher when another client is active at the same time, which for a launcher that launches launchers, this is not super unreasonable.
I want to also mention on the subject of the Steam plugin, my Steam library is enormous (almost 800 games). I wouldn't consider it unreasonable for a library of that size to take some time to scrape through. Depending on how often Galaxy is doing that, I could easily see it causing high CPU draws.
After this re-initiation, does GOG Galaxy peak back in CPU usage "immediately"?
Post edited October 29, 2019 by GenlyAi
DeusExMachina.630
New User
Registered: Oct 2008
From Germany
Posted October 29, 2019
I've encountered the same issue. The steam plugin is constantly generating around 7% of CPU-Usage. I don't know if it's related to the amount of games, but I've got around 3000 games on Steam alone. Apart from that it's working fine, though.