Open dustymabe opened 3 years ago
Yeah, I know :(
Do you have thread_messages_in_channel enabled? With the new API we have to do lots of API call to support that, which kills performance.
Yeah, I know :(
Oops. Sorry to poor salt in the wound.
Do you have thread_messages_in_channel enabled? With the new API we have to do lots of API call to support that, which kills performance.
Yes, I do have that enabled. It's quite a nice feature.
So the thing is that previously we only had to make one request for the history per channel, and we would get the history including threads. Now we have to make one request for the channel history, and additionally one request for each thread in the history we fetch. I don't know a way around this, but I would of course be glad if someone found a better way with the API. The old API doesn't work anymore, so we can't use that.
I also use that feature, so my solution is to basically almost never reload wee-slack, since only the startup is affected.
Interesting. Thanks for the context. I was able to bring things back to a more reasonable level by:
/set plugins.var.python.slack.background_load_all_history false
Which prevents trying to load a crazy amount of history up front. I think it was really killing my instance on this low power machine.
I just upgraded my low-resource weechat client box and notice very high CPU usage and slow performance to the point where just typing takes seconds sometimes. I was previously on
v2.6.0
with no issues. I did a bisect to find where the problem was introduced:Looks it was introduced with e626714. Can we look into what happened there and get our CPU usage back to a reasonable level?