[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-devel
Subject:    Re: Special purpose malloc() in KDE?
From:       David Faure <david () mandrakesoft ! com>
Date:       2001-03-25 20:49:43
[Download RAW message or body]

On Saturday 24 March 2001 18:09, Petter Reinholdtsen wrote:
> The last few days, I've been checking the perforance of GNU malloc
> (glibc v2.1.3 in Debian 2.2), and was shocked to discover how bad it
> behaved in our application.  The memory usage was almost stable on ~2
> MB, bu the process size was increasing several megabytes, starting at
> 15 MB, and eding above 30MB.  Using the mallinfo() stats, I discovered
> the amount of free memory increasing instead of being reused.  I
> expect this is due to bad memory fragmentation.
> 
> Replacing the malloc() implementation with Doug Lea's malloc(),
> available from <URL:http://g.oswego.edu/dl/>, changed the situation
> completely.  The process size stayed stable around 17MB, and the
> amount of free memory rarely moved above 200KB.
> 
> I've reported this as a bug to the GNU C library maintainers.
> 
> Is KDE using the normal malloc() implementation on Linux, or its own
> improved version?  Perhaps changing the malloc() implementation can
> reduce the memory usage?

KDE is written in C++, which uses new and delete, not malloc and free.

AFAIK this comes from libstdc++ or g++ itself, so it should be unrelated
to glibc's malloc (unless new uses it internally, I don't know).

-- 
David FAURE, david@mandrakesoft.com, faure@kde.org
http://perso.mandrakesoft.com/~david/, http://www.konqueror.org/
KDE, Making The Future of Computing Available Today

 
>> Visit http://master.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<

[prev in list] [next in list] [prev in thread] [next in thread]