omit to loop-forever processing some regex acls

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 - -- Matt Benjamin The Linux Box 206 South Fifth Ave. Suite 150 Ann Arbor, MI 48104 http://linuxbox.com tel. 734-761-4689 fax. 734-769-8938 cel. 734-216-5309 -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.7 (GNU/Linux) Comment: Using

fixup for URI decoration with port when not wanted

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Affects store keys and cache peering lookups. Matt - -- Matt Benjamin The Linux Box 206 South Fifth Ave. Suite 150 Ann Arbor, MI 48104 http://linuxbox.com tel. 734-761-4689 fax. 734-769-8938 cel. 734-216-5309 -BEGIN PGP SIGNATURE-

Re: Rv: Why not BerkeleyDB based object store?

Just a tangental thought; has there been any investigation into reducing the amount of write traffic with the existing stores? E.g., establishing a floor for reference count; if it doesn't have n refs, don't write to disk? This will impact hit rate, of course, but may mitigate in

Associating accesses with cache.log entries

I've been playing around with associating specific requests with the debug output they generate, with a simple patch to _db_print along these lines: if (Config.Log.accesslogs Config.Log.accesslogs-logfile) { seqnum = LOGFILE_SEQNO(Config.Log.accesslogs-logfile); }

Re: Associating accesses with cache.log entries

On Thu, Nov 27, 2008 at 4:21 AM, Mark Nottingham [EMAIL PROTECTED] wrote: I've been playing around with associating specific requests with the debug output they generate, with a simple patch to _db_print along these lines: if (Config.Log.accesslogs Config.Log.accesslogs-logfile) {

Re: Rv: Why not BerkeleyDB based object store?

I thought about it a while ago but i'm just out of time to be honest. Writing objects to disk only if they're popular or you need the RAM to handle concurrent accesses for large objects for some reason would probably way way improve disk performance as the amount of writing would drop drastically.

Re: omit to loop-forever processing some regex acls

G'day! If these are patches against Squid-2 then please put them into the Squid bugzilla so we don't lose them. There's a different process for Squid-3 submissions. Thanks! Adrian 2008/11/26 Matt Benjamin [EMAIL PROTECTED]: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 - -- Matt