Comment on Long load times again
Sal@mander.xyz 23 hours agoI have experienced issues both over tor and over clearnet. The tor front-end exists on its own server, but it connects to the mander server. So, the server that hosts the front-end via Tor will see the exit node connecting to it, and then the mander server gets the requests via that Tor server. Ultimately some bandwidth is used for both servers because the data travels from mander, to the tor front-end, and then to the exit node. There is also another server that hosts and serves the images.
What I see is not a bandwidth problem, though. It seems like the database queries are the bottleneck. There is a limited number of connections to the database, and some of the queries are complex and use a lot of CPU. It is the intense searching through the database what appears to throttle the website.
plantteacher@mander.xyz 7 hours ago
The onion eliminates the use of exit nodes. But I know what you mean.
I appreciate the explanation. It sounds like replicating the backend and DB on the Tor node would help. Not sure how complex it would be to have the DBs synchronise during idle moments.
Perhaps a bit radical, but I wonder if it would be interesting to do a nightly DB export to JSON or CSV files. Scrapers would prefer that, and it would be less intrusive on the website. Though I don’t know how tricky it would be to exclude non-public data from the dataset.