[BUG]: High cpu usage
How are you running AnythingLLM?
AnythingLLM desktop app
What happened?
When using the DeepSeek R1 model, the CPU usage is high when waiting for a response or rendering, almost using up all idle resources. Is it really necessary to consume such high resources when waiting for a response or rendering? Is this an unpredictable bug or is it software design? Hope to get a reply. Thanks
Are there known steps to reproduce?
No response
To be clear, you are not using the built in LLM are you? If you dont have a GPU and are running models on CPU some systems show the Renderer process as high CPU when really it is the main thread doing LLM Inference on CPU.
Outside of that, what are your system specs (CPU, RAM, OS) and what version of AnythingLLM Desktop are you on?
I'm not running any mods on the cpu, using a call to the api interface. My system related parameters are as follows: Cpu:M1Max 10cpu 32gpu System OS: macos 15.3.2 (24D81) Memory RAM: 32GB
And AnythingLLM Despktop Version: 1.7.7
Same here. In Ubuntu the AnythingLLM desktop uses constantly 40% CPU even when application has no activity in long time. I only use LLM's via API, no locals. Inactive ubuntu desktop app eating 40% CPU all the time, when it should be idle. I need to close the program when I don't use it to save CPU, otherwise my Lenovo laptop i7 23Gb RAM becomes too sluggish.
@jarkko-hautakorpi When in that state, is the application window totally minimized/hidden, or is it in the UI and just unused? Since all of this comes from the render process its not related to models or anything and almost certainly has to do with animations in the UI, however there should not be any animations in an idle state.
I'm also facing a similar issue. When it's not even in the foreground and I'm using some other app, it constantly keeps using CPU cycles in the background, as if it's doing something, but in reality, it's not.
I don't use any local models. I use all the APIs, so there's no question for it to be using that many CPU cycles.
I’m facing the same issue on Arch Linux with GNOME. The UI process alone consumes 100% CPU usage whenever the application window is open, even when no LLM or additional workloads are running. The problem does not occur when using KDE.