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.
Re: Re: Really struggling with windows install pls help :)
By: Digital Man to Matthew C E Bamber on Mon Jan 01 2024 03:48 pm
So I have an ip.can file that is about 1.3 gigs large, and when it gets this large there is a very long delay before a user can connect because I believe the bbs is working on parsing each line and seeing if the ip matches. I would assume I would have the same issue with host.can and other .can files.
I was wondering if there's anything I can do on my end to keep these large .can files and speed things up, or if synchronet needs some internal changes.
Thanks,
---
� Synchronet � ::: BBSES.info - free BBS services :::
| Sysop: | digital man |
|---|---|
| Location: | Riverside County, California |
| Users: | 1,151 |
| Nodes: | 17 (0 / 17) |
| Uptime: | 33:34:03 |
| Calls: | 509,174 |
| Calls today: | 10 |
| Files: | 291,658 |
| D/L today: |
38,640 files (6,642M bytes) |
| Messages: | 468,445 |
| Posted today: | 3 |