search

BlafKing / sd-civitai-browser-plus

Extension to access CivitAI via WebUI: download, delete, scan for updates, list installed models, assign tags, and boost downloads with multi-threading.
GNU Affero General Public License v3.0
329 stars 57 forks source link

[Bug]: Laggy UI (Forge Gradio 4+) #326

Closed younyokel closed 1 month ago

younyokel commented 2 months ago

Describe the bug.

The entire user interface in Forge is now slow to respond to user input compared to versions prior to Gradio 4

Steps to reproduce the problem.

  1. Compare performance with and without CivitAI Browser+

Expected behavior

--

System info

Console logs

--

Additional information

No response

nor1c commented 2 months ago

any update?

Terroosh commented 2 months ago

any update?

There hasn't been an update in 3 months. BlafKing might be busy or could have moved on from this project.

KuroNeko87 commented 2 months ago

Yeah, experiencing same issue. Feels like using browser when cpu/ram is at 100% but it isn't.

crsongbird commented 2 months ago

It maxes out one core of the CPU for some reason.

metapea commented 2 months ago

it's been also laggy on reforge for a while

Nisekoi-1 commented 2 months ago

same

BenjaminSymons commented 1 month ago

I've remedied the initial lag causing code in my fork and pull request here: https://github.com/BlafKing/sd-civitai-browser-plus/pull/339

Additional work is needed to remove the calls to tabs that are no longer considered tabs and commences a similar endpoint spam

younyokel commented 1 month ago

@BenjaminSymons Nice, I tried your fork. It seems to be less laggy compared to this version, but still lags a bit. I'm hoping you can make this work out.

prezofpizza commented 1 month ago

@BenjaminSymons I seem to get stock with the "Loading model info, please wait!" model and can't seem to figure out why. Only happens in Forge, Auto1111 is fine. Used console logs to check that parameters are set correctly, so not sure what could be causing the issue.

Has anyone else run into this?

younyokel commented 1 month ago

no way, seems to be fixed now

Can more people confirm

BlafKing commented 1 month ago

Should indeed be mostly fixed! Just merged the pull request #341 which contained code from @BenjaminSymons and @channelcat so you can all thank them for the initial fix! 🎉

I'm getting back into maintaining this project so I'll try my best to find the time to patch things up further wherever the issues still exist! (plenty of bugs left to catch 👀)

There are currently still a few performance issues left, so I'll try my best to find ways to optimise things further!

This issue should (mostly) be fixed now though, at least till the point where the UI doesn't become unusable anymore 😅 So I'll close this issue!