> Currently, the export is from April 2025 and affects all users and replies up to node id 210000.

But the process might still need adjustments, some discussion replies only show your home node. ¹

Like Re^4: A dedication to the Perlmonks ladies (node 200040) (change to domain without login to see ²)

Or do you only intend to cache root nodes with whole threads?(actually, the root node (200000) in the above mentioned thread doesn't seem to be cached at all)

As a technicality:

You might also want to add to the side effects of the caching that edits/updates of old nodes will also go undetected for the time being.

¹) vanity SEO? ;)

²) like probably www.~.net https://www.perlmonks.net/index.pl?node_id=200040

G'day Co-Rion,

I appreciate your efforts to improve the useability of the site. Thankyou.

I'll just report that I logged in about six hours ago — "Last here: Sep 19, 2025 at 16:08 UTC (6 hours ago)" — and experienced problems:

1. Connection to https://www.perlmonks.org/?node_id=861371 took a while but got there in the end.
2. Two attempts to login: both very slow; first timed-out.
3. Three attempts to access Nodes You Wrote: all timed-out.
4. Gave up and logged out.

I tried again just now and response was much improved; still a little slow but no time-outs.

One of the first things I did was to turn off the Slashdot & HackerNews nodelets. This resulted in a noticeable improvement in response time. I'm reasonably sure that those nodelets have been mentioned previously in relation to site sluggishness; maybe worth a revisit.

Nodelets certainly add load, but they are not the overall reason.

You might improve your personal experience by "some" percentage by deactivating all nodelets in your settings.( Which is a nice workaround thanks)

But I don't have your slashdot nodelet activated, and it took me today half an hour to get my post thru.

Cheers Rolf
_{(addicted to the Perl Programming Language :)
see Wikisyntax for the Monastery}