Filesystem for squid.
For xfs, try this:/dev/hde3 on /var/spool type xfs (rw,noexec,nosuid,noatime,osyncisdsync)But supposedly the best fs for squid is reiserfs, and you may like those options:
reiserfs (rw,noexec,nosuid,nodev,noatime,nodiratime,notail,block-allocator=noborder)Nice thing to remember is that squid is very HDD intensive application, so it's rather unwise to run in on anything slower then SCSI (like you can see above I'm running it ;) is asking for trouble... and dumb.
You should also consider oops instead of squid for following reasons:
- oops is more lightweight then squid
- it's way easier to set up and configure.
oopsctl statprovides hot stats in nice format- oops can use raw partitions as it's cache.
- oops very quick to stop and start. ( try /etc/init.d/oops restart -> few seconds, try /etc/init.d/squid restart -> few minutes ). And you don't wan't your users waiting for few minutes when you change something simple but requiring restart.
- oops provides special for for transparent proxy ( with squid you can use either transproxy programm, or configure your squid as transproxy, but if you do, prepare for troubles when you use it also as normal proxy)
- squid is rather old code, oops is young and developing vigorously. It's code is cleaner and smaller ( squid is well tested, but contains lots and lots of cruft accumulated for years).
- oops uses single file as it's spool, not some clunky array of arrays of directories. Way easier to manage.
Update:
Based on: http://conferences.oreillynet.com/presentations/os2002/wessels_duane.ppt best filesystem for squid cache is ext2fs, and worst is xfs ( no wonder... ). second best filesystem for squid seems to be reiserfs (notail,noatime), but ext2 is twice as fast as reiserfs in this scenario.| Filesystem for squid. | | 2004.03.13-19:20.00
