|
From: Decent E. <dec...@gm...> - 2025-08-21 17:08:34
|
Today we moved our production server https://decentespresso.com/ from navi4.99 (built 6 years ago) to release navi5. Wow, it’s quite a bit faster. I’m also curious to see if: 1 - the slowly growing memory footprint of nsd 4.99 is no longer happening 2 - if nsd no longer occasionally crashes Due to much increased load on the server due to AI company spiders, we made the move. We also moved all media file serving to a separate nginx process, just to remove a possible cause, and to reduce the possible causes. Every once in a while with nsd 4.99, we’d see a huge spike in cpu utilization, and couldn’t see anything in the access logs that was a likely cause. I do realize that #1 could be caused by my own code, or poor tracking of ns_cache. The only thing to figure out for us, is the “untrusted” https domains we host (we have a *.decentespresso.com ssl cert) and that looks like a config change, as the warnings indicate. And I believe that ns_cache is now deprecated, so I should look at replacing that. I make heavy use of this: proc content_cache {cachename codetorun} { if {[cookie_get "decent_admin"] != "" || [decentliveserver] == 0} { return [eval $codetorun] } return [ns_cache_eval tempfile $cachename $codetorun] } on pages that use big mysql queries to render. Anything else big in navi5 that I should jump on? -john |