the windows client constantly keeps a 3d rendering context (chrome) alive preventing my gpu from downclocking.
as long as the client is running, my GPU is tacted at 1.6 GHz, if i kill the client GPU settles at around 0.14 GHz. this makes quite the difference in power consumption of my machine when left idle for multiple hours the day.
nowadays i only start the client when i want to sync files or expect to receive some uploaded by my peers. after thats is done the client gets killed immediately.
but why does it have an 3d context running you ask? for the small notification window where i can track the sync progress. i still remember the "native" solution they used few years back, did not have drop shadows, but the entire functionality was present via an WinAPI menus. Considering one can, with some OwnerDraw work, put progress bars and scrollable lists in Menus, i don't get the point of using an whole web browser to display a 600x200 popup.
They really should take a look at bvckup2, how fast and efficient a backup/sync tool could be done in native way
as long as the client is running, my GPU is tacted at 1.6 GHz, if i kill the client GPU settles at around 0.14 GHz. this makes quite the difference in power consumption of my machine when left idle for multiple hours the day.
nowadays i only start the client when i want to sync files or expect to receive some uploaded by my peers. after thats is done the client gets killed immediately.
but why does it have an 3d context running you ask? for the small notification window where i can track the sync progress. i still remember the "native" solution they used few years back, did not have drop shadows, but the entire functionality was present via an WinAPI menus. Considering one can, with some OwnerDraw work, put progress bars and scrollable lists in Menus, i don't get the point of using an whole web browser to display a 600x200 popup.
They really should take a look at bvckup2, how fast and efficient a backup/sync tool could be done in native way