Henrik Nordstrom wrote:
> On ons, 2008-09-24 at 10:18 +0200, Henrik Nordstrom wrote:
>
>> For on-disk objects about 100 bytes.
>>
>> In-memory objects obviously uses a lot more. Probably something like 1kb
>> + the object size rounded up to 4k pages.
>>
>> Also disable the client db unless you nee
On ons, 2008-09-24 at 10:18 +0200, Henrik Nordstrom wrote:
> For on-disk objects about 100 bytes.
>
> In-memory objects obviously uses a lot more. Probably something like 1kb
> + the object size rounded up to 4k pages.
>
> Also disable the client db unless you need to use the maxconn acl
>
>
On ons, 2008-09-24 at 14:14 +1200, Martin Langhoff wrote:
> Good hint, thanks! If we did have such a control, what is the wired
> memory that squid will use for each entry? In an email earlier I
> wrote...
For on-disk objects about 100 bytes.
In-memory objects obviously uses a lot more. Probably
On tis, 2008-09-23 at 14:57 +0800, Adrian Chadd wrote:
> >> You can limit the amount of cache_mem which limits the memory cache
> >> size; you could probably modify the squid codebase to start purging
> >> objects at a certain object count rather than based on the disk+memory
> >> storage size. Th
On 23/09/2008, at 2:40 PM, Martin Langhoff wrote:
> On Tue, Sep 23, 2008 at 4:12 PM, Mark Nottingham <[EMAIL PROTECTED]
> inc.com> wrote:
>> Overall, what do you want to use Squid for here; caching, access
>> control..?
>
> Caching and plugins such as squidgard (does that qualify as access
>
On 23/09/2008, at 1:42 PM, Martin Langhoff wrote:
>
>> There's no "hard limit" for squid and squid (any version) handles
>> memory allocation failures very very poorly (read: crashes.)
>
> Is it relatively sane to run it with a tight rlimit and restart it
> often? Or just monitor it and restart it
