Would you suggest I go back to -N? I've not seen anything awkward or out of the ordinary in cache.log.. I downloaded and tried to build squid-5 from AUR.. squid -v Squid Cache: Version 5.0.0-20190909-ra70e75b76 Service Name: squid Intercept/WCCPv2/SSL/CRTD/(A)UFS/DISKD/ROCK/eCAP/ICAP/64/GCC Production This binary uses OpenSSL 1.1.1d 10 Sep 2019. For legal restrictions on distribution see https://www.openssl.org/source/license.html (had to go back a few days for a successful build..) root:/dev/shm # ls -al total 5876 drwxrwxrwt 2 root root 280 2019-09-18 15:15 . drwxr-xr-x 19 root root 3340 2019-09-18 06:52 .. -rw------- 1 proxy proxy 393232 2019-09-18 15:15 squid-cache_mem_ex.shm -rw------- 1 proxy proxy 3145840 2019-09-18 16:16 squid-cache_mem_map_anchors.shm -rw------- 1 proxy proxy 131080 2019-09-18 15:15 squid-cache_mem_map_filenos.shm -rw------- 1 proxy proxy 262156 2019-09-18 15:15 squid-cache_mem_map_slices.shm -rw------- 1 proxy proxy 131112 2019-09-18 15:15 squid-cache_mem_space.shm -rw------- 1 proxy proxy 8 2019-09-18 15:15 squid-cf__metadata.shm -rw------- 1 proxy proxy 32852 2019-09-18 15:15 squid-cf__queues.shm -rw------- 1 proxy proxy 52 2019-09-18 15:15 squid-cf__readers.shm -rw------- 1 proxy proxy 1073872936 2019-09-18 15:15 squid-squid-page-pool.shm -rw------- 1 proxy proxy 1572976 2019-09-18 15:25 squid-transients_map_anchors.shm -rw------- 1 proxy proxy 65544 2019-09-18 15:15 squid-transients_map_filenos.shm -rw------- 1 proxy proxy 131084 2019-09-18 15:15 squid-transients_map_slices.shm root:/dev/shm # uname -a Linux arch0033-0f2b4d 4.19.73-1-lts #1 SMP Mon Sep 16 17:15:25 CEST 2019 x86_64 GNU/Linux is this 'buggy' as well? Thank you for your interest in my question(s); greatly appreciated. On Wed, Sep 18, 2019 at 4:14 PM Alex Rousskov <rousskov@xxxxxxxxxxxxxxxxxxxxxxx> wrote: > > On 9/18/19 3:37 PM, B. Cook wrote: > > > this is /dev/shm with --foreground (no workers) > > > -rw------- 1 proxy proxy 8 2019-09-18 10:30 squid-cf__metadata.shm > > -rw------- 1 proxy proxy 8216 2019-09-18 10:30 squid-cf__queues.shm > > -rw------- 1 proxy proxy 36 2019-09-18 10:30 squid-cf__readers.shm > > Your Squid is buggy: These collapsed forwarding shared memory segments > should not be created for non-SMP configurations. Using these collapsed > forwarding segments might slow down a non-SMP Squid instance, but I do > not know whether they are actually _used_. I suspect they are not. > > The latest (future v5) Squid has the same bug AFAICT. > > Unfortunately, in my future-v5 tests, the same or similar bug exists in > Squids started with -N, so this bug is probably not a good suspect in > your investigation. I have no other suspects to offer at this time. > > Alex. > > > > On Wed, Sep 18, 2019 at 2:38 PM Alex Rousskov wrote: > > > >> One thing you may want to check is whether your --foreground Squid is > >> creating shared memory segments (look in /dev/shm/ or equivalent). > >> Creating shared memory segments in non-SMP configurations is a bug. > >> IIRC, we have fixed one or two of those bugs, but there may be more, and > >> using shared memory tables can decrease performance of non-SMP > >> configurations (there is no free lunch). > > _______________________________________________ > squid-users mailing list > squid-users@xxxxxxxxxxxxxxxxxxxxx > http://lists.squid-cache.org/listinfo/squid-users -- Network Analyst Poughkeepsie City School District SMS & Mobile: (202) 810-5827 twitter.com/bcookatpcsd If you can't explain it simply, you don't understand it well enough. -- This message may contain confidential information and is intended only for the individual(s) named. If you are not an intended recipient you are not authorized to disseminate, distribute or copy this e-mail. Please notify the sender immediately if you have received this e-mail by mistake and delete this e-mail from your system. _______________________________________________ squid-users mailing list squid-users@xxxxxxxxxxxxxxxxxxxxx http://lists.squid-cache.org/listinfo/squid-users
