Re: What is a "sane" setting for maxdsize when running amd64? it seems many normal suggestions do not apply.

[Dag-Erling Smørgrav <des_(_at_)_des_(_dot_)_no>]

Chuck Swiger <cswiger_(_at_)_mac_(_dot_)_com> writes:
> You should configure squid to use no more than about 60 - 70% of the
> available physical RAM-- ie, set the cache_mem parameter to about 2.5
> or 3GB.

Better yet, don't run Squid at all.  It was designed for a computer
architecture that was already obsolete when Squid was first written.

> It wouldn't be unreasonable to limit datasize to 3 GB on such a
> machine, assuming that nothing you run will ever need to grow
> larger...

...actually, maxdsiz is meaningless in FreeBSD 7, because the new
allocator uses mmap(2) instead of brk(2) / sbrk(2), so malloc() counts
towards the resident set size (ulimit -m), not the data segment size
(ulimit -d).

(unless, of course, your application has its own allocator, in which
case you can kiss performance goodbye)

DES
-- 
Dag-Erling Smørgrav - des_(_at_)_des_(_dot_)_no
_______________________________________________
freebsd-amd64_(_at_)_freebsd_(_dot_)_org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-amd64
To unsubscribe, send any mail to "freebsd-amd64-unsubscribe_(_at_)_freebsd_(_dot_)_org"