We're looking to repurpose an excess Server, the Supermicro Xeon-D 1587 (16c/32t). It was bought on another budget with excess everything, Max RAM (128GB), 480GB NVME SSD, 1 TB SATA-SSD. We have a lot (2200 iPads) of internal Mobile Clients that download large databases from the Internet, approx. 32GB each per month. (changes monthly).
Anyone with experience with Squid or the Xeon-D have any big glaring mistakes visible? Obviously I am going to tune the caching towards memory where possible, and define some dynamic download specifics to make sure they cache properly, but am I missing something stupid like Squid's poor threading? The network itself is solid. Server would have a 10GB network connection and some turbo-Wifi throughout the usage area. Its the WAN I need to solve with caching, but not if the processing/IO is going to die in the process.
Bryan
Anyone with experience with Squid or the Xeon-D have any big glaring mistakes visible? Obviously I am going to tune the caching towards memory where possible, and define some dynamic download specifics to make sure they cache properly, but am I missing something stupid like Squid's poor threading? The network itself is solid. Server would have a 10GB network connection and some turbo-Wifi throughout the usage area. Its the WAN I need to solve with caching, but not if the processing/IO is going to die in the process.
Bryan
Last edited: