|
|
| Perl: the Markov chain saw | |
| PerlMonks |
Re^5: Perlmonks site has become far too slowby LanX (Saint) |
| on Aug 31, 2025 at 19:19 UTC ( [id://11166149]=note: print w/replies, xml ) | Need Help?? |
|
Some remarks/ideas for the logs: > Every page is several database accesses getNodeByID in Everything/NodeBase.pm is using a cache when accessing the DB.
see also Everything/NodeCache.pm I suppose the gods have increased the cache-size from the initial 300 in Everything/NodeBase.pm?
Does the caching prioritize based on access count, I have to admit this is not easy to grasp. > so there is no set of "hot" nodes. there is no set of hot posts (which are internally nodes) but specific code and html nodes certainly are heavily used internally (AFAICS is 99,9% of the monastery held in DB-nodes) > and several Perl eval calls using memoization of in Everything/HTML.pm might help here to avoid unnecessary compilations
(tho there might be a side effect of pre-compiling into an extra sub layer) something like (untested)
html cachingan internal caching of the result of std_node_display into the DB might help too, but here plenty of side parameters need to be taken into consideration. A caching for Anomonk alone must take into consideration (at least)
The "print view w/o replies" is already close, but doesn't include links to children replies yet. compare https://perlmonks.org/?node_id=11164875;displaytype=print
Cheers Rolf
In Section
Perl Monks Discussion
|
|
||||||||||||||||||||||||||||||