Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 26 Mar 2013 22:08:33 +0200
From:      Alexander Yerenkow <yerenkow@gmail.com>
To:        Tony Li <tony.li@tony.li>
Cc:        Unga <unga888@yahoo.com>, "freebsd-stable@freebsd.org" <freebsd-stable@freebsd.org>
Subject:   Re: FreeBSD 9.1 excessive memory allocations
Message-ID:  <CAPJF9w=ZpVzFrh-5yd6aHGRa-NuFB-PJ2ZAPEiL44ThXfNkEDw@mail.gmail.com>
In-Reply-To: <175E75EE-8E85-49A4-838B-D79CE96CC3C4@tony.li>
References:  <1364322902.78474.YahooMailNeo@web161904.mail.bf1.yahoo.com> <175E75EE-8E85-49A4-838B-D79CE96CC3C4@tony.li>

next in thread | previous in thread | raw e-mail | index | archive | help
2013/3/26 Tony Li <tony.li@tony.li>

>
> > I have a heavily threaded C application, developed on an Intel Core i5
> laptop (2 cores) running FreeBSD 8.1-RELEASE.
> >
> > When this application compile and run on another Intel Core i7 laptop (4
> cores) running FreeBSD 9.1-RELEASE, this application immediately starts
> grabbing memory by over 100MB per second and soon exit with not enough RAM.
>

Sorry, can't remember exactly, but you could search current- or stable-
 for something like you got.
This related IIRC with changes in thread subsystem, so basically each
thread will consume now more mem.
Search for details, your description is ringing some bell :)

> >
> >
> > Both laptops having 4GB RAM.
> >
> > All malloc and free are mutex locked.
> >
> > Very rarely this problem happens on the i5 (2 cores) laptop too, but on
> the i7 laptop, it happens every time.
> >
> > Appreciate any feedback to identify and fix this issue.
>
>
> How is this anything except an application issue?
>
> Tony
>
> _______________________________________________
> freebsd-stable@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-stable
> To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org"
>



-- 
Regards,
Alexander Yerenkow



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAPJF9w=ZpVzFrh-5yd6aHGRa-NuFB-PJ2ZAPEiL44ThXfNkEDw>