Re: large *.can files make things slow
  By: MRO to Digital Man on Tue Jan 02 2024 01:37 pm

 >  > memory for all of SBBS to have that massive ip.can file cached. It can be
 >  > done and would likely have a significant performance improvement, but at
 >  > the cost of a lot of memory used (in your case).
 >
 > i guess i'll just trim it down every month.

If you have the available RAM, it wouldn't be a bad option to have. In fact, when importing QWK packets, the ip.can file *is* cached (since the source IP address of each message is compared, and that'd be really slow to re-read the file each time) - so there's already some cases where your SBBS instance is allocating that much RAM for the ip.can file, but for a shorter period of time since that memory is freed after QWK packet import is complete. For a server that's listening for incoming TCP/UDP connections, the memory (for the ip.can cache) wouldn't be freed until the server was terminated.
-- 
                                            digital man (rob)

Synchronet "Real Fact" #35:
The irc.synchro.net network has more servers than users
Norco, CA WX: 60.9øF, 57.0% humidity, 0 mph NE wind, 0.00 inches rain/24hrs
--- SBBSecho 3.20-Linux