[Bug libc/11044] malloc dynamic mmap threshold causes 50%-100% increase in memory usage

[Bug libc/11044] malloc dynamic mmap threshold causes 50%-100% increase in memory usage

[jackie.rosen at hushmail dot com]

https://sourceware.org/bugzilla/show_bug.cgi?id=11044

Jackie Rosen <jackie.rosen at hushmail dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |jackie.rosen at hushmail dot com

--- Comment #6 from Jackie Rosen <jackie.rosen at hushmail dot com> ---
*** Bug 260998 has been marked as a duplicate of this bug. ***
Seen from the domain http://volichat.com
Page where seen: http://volichat.com/adult-chat-rooms
Marked for reference. Resolved as fixed @bugzilla.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Bug libc/11044] malloc dynamic mmap threshold causes 50%-100% increase in memory usage

[schwab at sourceware dot org]

https://sourceware.org/bugzilla/show_bug.cgi?id=11044

Andreas Schwab <schwab at sourceware dot org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|jackie.rosen at hushmail dot com   |

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Bug libc/11044] malloc dynamic mmap threshold causes 50%-100% increase in memory usage

[fweimer at redhat dot com]

https://sourceware.org/bugzilla/show_bug.cgi?id=11044

Florian Weimer <fweimer at redhat dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
              Flags|                            |security-

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Bug libc/11044] malloc dynamic mmap threshold causes 50%-100% increase in memory usage

[tom at atoptech dot com]

------- Additional Comments From tom at atoptech dot com  2010-04-07 17:09 -------
Ulrich,

I filed this bug to show, at least for our application, this change did not
result in improved performance. To the contrary, this change increase memory
fragmentation and in some case, memory usage when from 32GB to 64GB when running
our application. Our application ran fine on RedHat release 3 and 4. When we
ported to release 5, memory usage increased with out reason. From our standpoint
we would like the compute platform to be stable from one release to the next.

All I wanted to point out was that after reading the patch comments for this
change, such as,

+  The threshold goes up in value when the application frees memory that was
+  allocated with the mmap allocator. The idea is that once the application
+  starts freeing memory of a certain size, it's highly probable that this is
+  a size the application uses for transient allocations. This estimator
+  is there to satisfy the new third requirement. 

seem to me; weakly justifiable. Some applications may exhibit this behavior,
however, our application does not. And if one going to try and dynamically
adjust the mmap threshold, one should keep adjusting the mmap threshold over the
lifetime of the process and not clamp it so early, i.e., based upon the first
free...

Regards,

Tom Geocaris



-- 


http://sourceware.org/bugzilla/show_bug.cgi?id=11044

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.

[Bug libc/11044] malloc dynamic mmap threshold causes 50%-100% increase in memory usage

[drepper at redhat dot com]

------- Additional Comments From drepper at redhat dot com  2010-04-05 18:34 -------
(In reply to comment #2)
> That is the point. This change had no statistical basis proving that it improved
> the malloc behavior on average (at least I'm not aware of any papers on the
> subject).

Appropriate measurements were made.  We don't require "papers" for every change
made.  Go to academia if you you want that.

The changes showed improvements and there are ways to turn the changes off.  You
cannot possibly ask for more.


-- 


http://sourceware.org/bugzilla/show_bug.cgi?id=11044

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.

[Bug libc/11044] malloc dynamic mmap threshold causes 50%-100% increase in memory usage

[drepper at redhat dot com]

------- Additional Comments From drepper at redhat dot com  2010-04-05 18:31 -------
(In reply to comment #2)
> That is the point. This change had no statistical basis proving that it improved
> the malloc behavior on average (at least I'm not aware of any papers on the
> subject).


> 
> > Aside, you are not reporting anything about current releases.
> 
> Correct me in I'm wrong, but this change is in the current release.
> 
> Regards,
> 
> Tom Geocaris



-- 


http://sourceware.org/bugzilla/show_bug.cgi?id=11044

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.

[Bug libc/11044] malloc dynamic mmap threshold causes 50%-100% increase in memory usage

[tom at atoptech dot com]

------- Additional Comments From tom at atoptech dot com  2010-04-05 16:10 -------
Ulrich,

> No malloc can work perfectly in all situations....

That is the point. This change had no statistical basis proving that it improved
the malloc behavior on average (at least I'm not aware of any papers on the
subject).

> Aside, you are not reporting anything about current releases.

Correct me in I'm wrong, but this change is in the current release.

Regards,

Tom Geocaris

-- 


http://sourceware.org/bugzilla/show_bug.cgi?id=11044

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.

[Bug libc/11044] malloc dynamic mmap threshold causes 50%-100% increase in memory usage

[drepper at redhat dot com]

------- Additional Comments From drepper at redhat dot com  2010-04-05 05:08 -------
No malloc can work perfectly in all situations.  This is why mallopt exist.  So,
use it.

Aside, you are not reporting anything about current releases.

-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |WONTFIX


http://sourceware.org/bugzilla/show_bug.cgi?id=11044

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.