@indexlibrorum said in FAF is using up a tremendous amount of power:
I've always found that the FAF client feels very sluggish and heavy for what it needs to do. We could use someone with the necessary knowhow to remake the thing from scratch.
More generally remaking it from scratch likely wouldn't solve any of the issues and it would be a lot of work with how many features the client has.
And on the note of the client feeling heavy I have basically been spending the last year focusing on reworking nearly the entire client backend and how the frontend works in order to drive down both the memory usage and CPU usage as well as eliminate a significant number of small memory leaks. As well as ensure the client is more aggressive about giving ram back to the os. (Although this did get interrupted a bit by needing to deal with the DDOS)
From my own measurements ram usage has been decreased by about 50% and CPU usage has drastically dropped outside of the recent reverse due to the chat changes.
Further more unfortunately I have seen that the actual usage can vary quite a bit depending on ones CPU architecture, and unfortunately I only have one architecture I can develop and debug on, so some things are just impossible to resolve but this is going to be true regardless of the UI technology you choose.
So in summary efficiency work on the client continues to go on and has been the focus over adding any new features this last year. It is just a slow and in depth process. Small exception this past month as I got deep into upgrading and adding some chat features that will come out in the next release with the caveat that new features always bring new fascinating bugs XD.