Open BloodyIron opened 1 year ago
This is a continuation from #2427 as @stickz recommended I create a new issue for the load performance I saw for action.php.
Try setting RU_REMOVE_CORE_PLUGINS
to false
on the docker install script. This will enable httprpc
which is faster than rpc
. It uses JSON
instead of XML
to communicate with the web browser. There is a slight overhead, but it may be worth it.
https://github.com/crazy-max/docker-rtorrent-rutorrent
@BloodyIron I'm waiting for a follow up. Anther possible cause is requiring a SSL certificate attached to a domain name to properly cache files in your web browser. 500ms is very optimistic and requires a perfect configuration.
@stickz sorry, life stuff, haven't had the time to properly re-test it yet and I will when I do. Hopefully in the next handful of days.
I am using a Let's Encrypt proper cert for the FQDN for the webGUI, served as part of the k8s Deployment via nginx Ingress.
Sounds good. The latest docker image has a more optimized curl
build now. This could help reduce loading times as well.
setting RU_REMOVE_CORE_PLUGINS to false
has not sped things up at all :(
getplugins.php is taking ~6.6 seconds now :/ and I also had to re-check all my torrent files after clearing the disable list... that was very long
Also, sorry for the delayed response to try this. Life stuff.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
It's still slow...
Please complete the following tasks.
Tell us about your environment
Vivaldi, browser Using: crazymax/rtorrent-rutorrent:latest (as of this writing ruTorrent v4.0.4)
Tell us how you installed ruTorrent
In the container already built
Describe the bug
Page already cached in browser, loading new page, or refreshing, page takes about 2 seconds to load, and action.php is invoked multiple times. Browser waterfall reports load times of action.php ranging 800ms to 2s.
Steps to reproduce
It happens every time on load, once it is already cached. Just go to page and it happens immediately.
Expected behavior
I'm of the understanding the total page load time at this point should be in the realm of about 400ms, so this increases the total load time by about 200%-500%.
Additional context
No response