Date: Thu, 03 Jan 2008 01:15:46 -0500 From: Joe Marcus Clarke <marcus@FreeBSD.org> To: Jason Evans <jasone@FreeBSD.org> Cc: Robert Watson <rwatson@FreeBSD.org>, current <current@FreeBSD.org> Subject: Re: Memory problem with latest malloc.c Message-ID: <1199340946.64371.14.camel@shumai.marcuscom.com> In-Reply-To: <477C7CB6.8080701@freebsd.org> References: <1199314166.9913.63.camel@shumai.marcuscom.com> <477C47BC.1020101@freebsd.org> <1199340028.64371.9.camel@shumai.marcuscom.com> <477C7CB6.8080701@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
--=-iX0YyCDUvry13VmnZCVM Content-Type: text/plain Content-Transfer-Encoding: quoted-printable On Wed, 2008-01-02 at 22:12 -0800, Jason Evans wrote: > Joe Marcus Clarke wrote: > > On Wed, 2008-01-02 at 18:26 -0800, Jason Evans wrote: > >> It would be really helpful to me if you run your program with=20 > >> MALLOC_OPTIONS=3DdM and monitor memory usage. These flags cause mmap = to=20 > >> be used instead of sbrk, and we can find out from that how much memory= =20 > >> you really need. If peak memory usage is substantially different when= =20 > >> using mmap versus sbrk, there's probably a malloc bug. > >=20 > > Memory climbed up to 976 MB SZ, 974 MB RSS MB with dM > > -> /etc/malloc.conf. The file was eventually generated without error. > > Again, with Aj -> /etc/malloc.conf, the python2.5 process operating on > > the same file planed out at 504 MB SZ, 501 MB RSS. >=20 > Okay, that indicates that there is not a problem with malloc; you're=20 > running into the data segment resource limit. It isn't possible to=20 > increase the data segment beyond 512 MB on i386, so your best bet is to=20 > use MALLOC_OPTIONS=3DDM for the memory-intensive program. That will caus= e=20 > the program use all available space in the data segment, then start=20 > using mmap as necessary. Yeah, I just realized that after looking at the memory usage of rev 1.154 (it's the same). I could tweak kern.maxdsiz in loader.conf, but ~ 1 GB is way too much memory for this program. I know what causes the extra memory usage, so I think I'll bug the Evolution guys. Thanks. >=20 > I'm sorta thinking that MALLOC_OPTIONS=3DDM should be the default. Rober= t=20 > Watson is the person who talked me into this change, so feel free to=20 > give him a hard time about the extra configuration you have to do in=20 > order to get work done. =3D) It may not be obvious to all users and I think many will be bit by this (i.e. POLA violation) considering maxdsiz is 512 MB on i386. Having DM the default would be a good idea IMHO. Joe --=20 Joe Marcus Clarke FreeBSD GNOME Team :: gnome@FreeBSD.org FreeNode / #freebsd-gnome http://www.FreeBSD.org/gnome --=-iX0YyCDUvry13VmnZCVM Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (FreeBSD) iD8DBQBHfH2Sb2iPiv4Uz4cRAs9uAKCQ7JFF+eCVwQ84yOpTYqhA9GRRggCfdpGX VUw9LVEs0fgx6o5gRDDerpc= =CpL4 -----END PGP SIGNATURE----- --=-iX0YyCDUvry13VmnZCVM--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1199340946.64371.14.camel>