PathOfBuilding icon indicating copy to clipboard operation
PathOfBuilding copied to clipboard

Unexpected GPU usage level while viewing a build Tree

Open E2A4E789A3DCC7236FF998692ADE60E2 opened this issue 2 years ago • 5 comments

Check version

  • [X] I'm running the latest version of Path of Building and I've verified this by checking the changelog

Check for duplicates

  • [X] I've checked for duplicate issues by using the search function of the issue tracker

What is the expected behaviour/value?

Normally PoB process GPU resource consumption was quite moderate. Baseline power draw for my rig is: 8 Watt on desktop 15W with PoB opened (before patch 2.20) 90W with Path of Exile client instance active

What is the actual behaviour/value?

Since 2.20 release PoB instance draws 35W from my GPU while idling with Tree tab active. The resource consumption goes high upon switching to the Tree view even with empty build tree.

How to reproduce the issue

No response

Character build code

eNqtWltz4rgSfp79FS7eJ4RLspktslsESEJVmOEEZuacpylhN6CNbFGWTML--tOSbHASZGRl5yFjrP661Re1uiX3_nqJWbCFVFCeXDdaZ-eNAJKQRzRZXTe-z28_XzX--vO33pTI9bflTUaZGvnzt089_Rww2AJD3DniJElXIH8UvDq_8N2GJHINPJmQv3l6x6PrxleeQCNYkCSisvgVMiLEVxLDdWMWIrgREBFCEg0O7w1hTGgy4-ETyLuUZxsU3Ai2FJ4nPEKa8WT67XFeEkqTslCc9afelJEdpDNJZCDwz3Wjj8qTFQxJjH-RG2EZsjo_a7UuG83jkNkGINqTts7aNsJpCqPlEkJJtzBIqRysSRKWhNhwdWknGZN0wyikpVld2BD375i3v9ho51wSNpzOyobpfGlXk3N5eto_qVzfMLSjO3MFGa8SKqEeZsqp4El9JV4hrObPGMMV4UbL4wVN6qg8IQkZcOFgzwe6BDfK0cyN7hHXgxulmuUUUlyx0n2ytQC5hBmEHLNCHRl1ICU9_IR5IEczH4CHoJk8JIe2lWoILw5U40Q68dpyqbP5qbnpFTe6nx6yV_tL15pU1ztBQ8Im5IXGWYzZbE6eIClhu1d2P63WMsH1agP_fmWd5C1NwQM24Czyga0JFx44FYlOpsBNLPxDUY-T0C3AvycpCEi35b2v0tZLeMQAVfvrgoEz5iAmD_QD8vy8WtgKEjdVHgDC9R0WE49Eglti2FNddruVNlXETjZVhEdsWsH_NaKGeRTwtXlarbNOFXVNC_0kaeSQuxJIV7vZmgKrSZ0H0m5ANg6pTrmhjHZyx2txTqFUhtQ02GhLRDk3VlabqI0hd4srwLoKARG41pDTlP-tqlRWD9ZPY56ljv4wxE4KFBne1OSPEGWh2z5yw7A3cJ09zoqxWoi-lCR8GvJoBbWE1EfMss0Gl7lyuStObU-PIGipFvh86UD9DZeV06pSG5m7gAO1s4D95uwu5Q3EXRe1u9ZQ5kDuLGLf-E0wccWYp3XXiI3qYclbnYM9hVNDoQkdG5Upf8aZr1WPLupRYxWyB1j3jNsUkn92zvxfkTsJGCVRlqql4CzjLeKYmDmNMVsKMSSSBAJIGq4f0MvXjUbp1y1hbIErH98qVK-pzz7U0zje8FTqlwPCQqF5jpNNJoNEH1vEVIS_FtlyqU4okKdM9cHK6PZ2NJiPf4zyaZQh4oky9ivJ4oVq583_h2CZgc6FgcgWwjxeN35QeJ4p1BAkoQxNE3LGyEZAdN1YEiZQMsVHTTNDfUNZwU1TYclZnIgc53UgsHMavUAqUV8sDsKUgnVe-_ETkzICVR2g3Gbjpo4f7IxMDh8QIc0-bbGUPuGxc1GHLlZ11GAFFmOGMKvkfPSEJeRuAwJ3VbqkoYr4apfPkdpQVdglDHGxhLsKf-c7kZ2HPs-xMTCDdrA5pbGh89EKq-qDIatVzagdPoSQWHU3g3bwvvTjCZrJxmVPVcHpK090kOOi6VOmdg2rZ0cM9iR2ht_kGlKzFVk5TTBHFSSVCyeli0zal3GJosJWuj-1WEiN2aGmC7PooMYqMtGrxsNi0DKNnZXpdKyJrApa1MsW85nRCiWKlsEy_3zYzsBUMFb_5fVQ1frGYtm-vtWgHWzWx3sWMs0cOehYHsISMAtVBvOepiKLyiwZYsKTFQZ1ZGV2pf6W08hU6h_ippU8zuxgqVq8TJI4arfaHHUn81HTv2lw_hXz5-djlvxdIjnBCBPvfcXW7sZpX_rfA2Hq_oGzjzF8dw74IT25FCSJhuqIw1nRXrOob3u6pBCBwML3DmJxs8P241YlzTcXHDGRuN9B_KCuCOdcFeEklJA-mCvDXBjRhsorU6kv9F5xLoI0giXJmHr_n4wwKnf65Ln0OmebULS1WPNnFWGGkSp_BObXhwcz0mcy56GkFDMx9srnoW3QyjU3CqvHeQpQzBirL0ViYPijfGU5jlRbghYQqO8u31tVT5FgF4APF1dXnU4jkMiudF3a-pLfhBq44vyp9_3xQT98Wku5EX80m8_Pz2cbItd8CS-UwVnI4-YGQTinz7p1-KzYNvv472bV1_80o2bBqWcuUIWJkKaau1ZTKacevnLcwdWYeln80KqrPiNvi2YyVfr8w3n8P62rMiyGu5yQTe4ENZY7pZO7BGvQIUVrpHpRF65VhP8t-rjeWKJTciOr5yIqMgHmuuMnkA1P9Gslx_RPhtBKlPsz15_xotcyZEFr9kw2QX-xE4KwwNgnuEAUsjXOaFqhb2FtN1g11Q3HReo5oWO6nJjUDTBZE3KLgfoUdJym1D42pY6fed2M0P6XYF2_SV76Sbv0t6ZPPJ3wwD1g4SDrCjoSSZc-ck6E3x3jW1XM1Gfc8V9FLR95Xb9YaPlFXve0e1wMW5ftsfDyVNwp71x4zMcjB3ZOiYl2gWnbarrvuJW94uvCB-S0JF0c4aXnhbdZ2x5-v_RbSR2_8O3Uj7Kuf9r3iOmWt_E7LgHRdSHymPYHih9HT_p74dIjKv3d8IFwcU3JCuu4atxJPSz3iO24WyVQO1FYzeuZLtz96aNOx8FOLX83dL2tdeGjjct68Q_yE1Pqxxk7srf1mnkPqXth3YTqWz2eLOnq3R3d2y-MDzd7-kvj95d6kEC8G4sbLsRJ2rffTJ8EmI-pj5JNGQlhzVkEaXkm-RfMxeXi7-Uvh47Rqyut4j6wAHUcMMXHCwXmohry-sOP0uVn8Tlgr1k4pNd8-0n6_wEaYuy2

Screenshots

No response

On my (oldish) PC: 2.19.1 = 55w 2.20.1 = 63w 8w (7.8%) difference

Nightblade avatar Aug 17 '22 12:08 Nightblade

This PR should help improve the performance, and therefore the power usage: #4776

I haven't looked at the engine code (i don't know if it is available)

But for a UI intensive program, i think they should lower the framerate to a bare minimum (10 FPS), and only render new frames on UI changes (i can't check right now, but they might be already doing that)

ryuukk avatar Aug 17 '22 23:08 ryuukk

@ryuukk https://github.com/PathOfBuildingCommunity/PathOfBuilding-SimpleGraphic

Nightblade avatar Aug 18 '22 02:08 Nightblade

I was just about to open an issue regarding that matter, but then I found this one.

If PoB isn't in focus nothing really happens in terms of resources used, as both CPU + GPU idle at around 1%, but once I focus PoB, and even if it's a completely empty tree with no passive points used, no skills, no items and not even searching for anything activities are skyrocketing: 00 01

ghost avatar Sep 10 '22 11:09 ghost

I just installed PoB on my new PC with a RTX 3080. I am experiencing the same issue. I also see that Desktop Window Manager also spikes but only when PoE is open. Using the Tree tab with PoE open in the background is impossible. The GPU goes to 100% usage across both PoB and Window Desktop Manager

NoxideLive avatar Dec 10 '22 02:12 NoxideLive