public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "sjmunroe at us dot ibm dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sources.redhat.com
Subject: [Bug libc/1541] Poor threaded application performance when using malloc
Date: Tue, 01 Nov 2005 17:19:00 -0000	[thread overview]
Message-ID: <20051101171924.16846.qmail@sourceware.org> (raw)
In-Reply-To: <20051025141150.1541.sjmunroe@us.ibm.com>


------- Additional Comments From sjmunroe at us dot ibm dot com  2005-11-01 17:19 -------
Created an attachment (id=734)
 --> (http://sourceware.org/bugzilla/attachment.cgi?id=734&action=view)
profile from similar run but with MMAP_THRESHOLD increased to 16M

Increasing the MMAP_THRESHOLD improved performance so I had the increase the
number of iterations to get the test to run long enoigh to profile. The profile
show most of the time (92%) in the test application (run_test) and and a few
percent in the malloc runtime. The first kernel contribution starts at 0.2% for
schedule.

-- 


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

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


  parent reply	other threads:[~2005-11-01 17:19 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-25 14:11 [Bug libc/1541] New: " sjmunroe at us dot ibm dot com
2005-10-25 15:32 ` [Bug libc/1541] " sjmunroe at us dot ibm dot com
2005-10-25 15:53 ` sjmunroe at us dot ibm dot com
2005-11-01  8:05 ` roland at gnu dot org
2005-11-01 17:12 ` sjmunroe at us dot ibm dot com
2005-11-01 17:19 ` sjmunroe at us dot ibm dot com [this message]
2005-11-01 17:27 ` sjmunroe at us dot ibm dot com
2007-02-18  4:45 ` drepper at redhat dot com
2010-06-01  3:30 ` pasky at suse dot cz
     [not found] <bug-1541-131@http.sourceware.org/bugzilla/>
2014-02-16 19:41 ` jackie.rosen at hushmail dot com
2014-05-28 19:46 ` schwab at sourceware dot org

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20051101171924.16846.qmail@sourceware.org \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=glibc-bugs@sources.redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).