You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
On my case each call returns almost 600kb of json data.
I have 12 feeds with 200 history results.
If i decrease the 200 to smaller value , the 600kb goes down in a linear manner.
When accessing the web GUI on lan , it not really noticed , but accessing it via the internet/vpn/app it is really slow.
Steps to reproduce
Just setup few RSS feeds with data and check your browser developer tools for traffic.
Additional context
I think the approach of the GUI is to "Fetch all" every time did not take lots of data scenario into account.
Some solutions as i can see think of :
1.Dont refresh the RSS feed page all the time , maybe once per entry is enough or after some more events. (add a refresh button ?) <- seems most simple
2.Add an option to reduce refresh rate to be user customizable , in my case every 5-10 seconds would be great.
3.API change to handle only delta between requests , so we don't re-transmit the whole rss feeds data every time.
Log(s) & preferences file(s)
No response
The text was updated successfully, but these errors were encountered:
qBittorrent & operating system versions
qbittorrent : 4.6.2
OS : debain 11
What is the problem?
Once entering rss feeds tab the traffic on the browser starts to get really high.
It seems the GUI calls about every 1 seconds for :
http:///qbit/api/v2/rss/items?lsrbvyqf&withData=true
On my case each call returns almost 600kb of json data.
I have 12 feeds with 200 history results.
If i decrease the 200 to smaller value , the 600kb goes down in a linear manner.
When accessing the web GUI on lan , it not really noticed , but accessing it via the internet/vpn/app it is really slow.
Steps to reproduce
Just setup few RSS feeds with data and check your browser developer tools for traffic.
Additional context
I think the approach of the GUI is to "Fetch all" every time did not take lots of data scenario into account.
Some solutions as i can see think of :
1.Dont refresh the RSS feed page all the time , maybe once per entry is enough or after some more events. (add a refresh button ?) <- seems most simple
2.Add an option to reduce refresh rate to be user customizable , in my case every 5-10 seconds would be great.
3.API change to handle only delta between requests , so we don't re-transmit the whole rss feeds data every time.
Log(s) & preferences file(s)
No response
The text was updated successfully, but these errors were encountered: