Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

www/squid: change cache_dir from ufs to rock #4487

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

AndyX90
Copy link
Contributor

@AndyX90 AndyX90 commented Jan 21, 2025

This pull-request changes the type of the squid cache_dir from ufs to rock.
We already included the workers in #4393 for smp-mode and should also move to rock as the cach_dir type, as rock is currently the only SMP-aware cache_dir type.

Testing happened on OPNSense 24.7.12 with enabled local ufs cache.
Switched to rock and it initialises the rock db in /var/squid/cache.
The pre-rock ufs data stays there until a reset via Squid Web Proxy --> Administration --> Support --> Reset is done.

More information: http://www.squid-cache.org/Doc/config/cache_dir/

@AdSchellevis
Copy link
Member

The question is if we shouldn't offer a choice here, when switching from one storage type to another, quite some side-affects might happen (such as excessive disk usage due to duplicate caches). The diskd type might be less destructive by the way, but I haven't looked at the performance differences.

@AndyX90
Copy link
Contributor Author

AndyX90 commented Jan 21, 2025

@AdSchellevis Thats a good question. My intention was to keep it simple and only support a cache_dir that is valid for all scenarios. Performance wise i read about the longer initialisation of the cache dir, but that doesn't affect squids startup. I also was not able to see any performance-regression in comparison to ufs(but my testing-cache was rather small). Related to the point of duplicate caches, i think it would be enough to make a note in the changelog, that squid content should be resettet via the ui once after the update to remove the old cache data.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

2 participants