git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Pat Thoyts <patthoyts@googlemail.com>
To: marius@trolltech.com
Cc: git@vger.kernel.org, msysgit@googlegroups.com
Subject: Re: [msysGit] Re: [PATCH] Add custom memory allocator to MinGW and  MacOS builds
Date: Fri, 3 Apr 2009 21:12:11 +0000	[thread overview]
Message-ID: <a5b261830904031412o60b7eb4fv7e25a2ca4f89fe60@mail.gmail.com> (raw)
In-Reply-To: <49D61B35.8060508@trolltech.com>

2009/4/3 Marius Storm-Olsen <marius@trolltech.com>:
>
> Marius Storm-Olsen said the following on 03.04.2009 15:52:
>> The standard allocator on Windows is pretty bad prior
>> to Windows Vista, and nedmalloc is better than the
>> modified dlmalloc provided with newer versions of the
>> MinGW libc.
>
> Actually, it just struck me that it's probably the synchronization
> primitives which are better on Vista than XP, and not the memory
> manager? (Since mingw 4.3.3-tdm on XP and Vista most likely use the
> same dlmalloc fork?) ^shrug^
>
> Anyways, not that I haven't tried to 'tune' nedmalloc in any way, just
> ensured that it compiles with the different MinGWs which I
> benchmarked. So, if anyone feels like it, maybe we can squeeze more
> performance out of it by tweaking it.

The difference on Windows Vista is that the low fragmentation heap is
the default memory allocator. On Windows XP you need to enable it
specifically for an application. So a possible alternative to this is
just to enable the low fragmentation heap. (done via GetProcessHeaps
and HeapSetInformation Win32 API calls).

Pat Thoyts

  reply	other threads:[~2009-04-03 21:13 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-03 13:52 [PATCH] Add custom memory allocator to MinGW and MacOS builds Marius Storm-Olsen
2009-04-03 14:20 ` Marius Storm-Olsen
2009-04-03 21:12   ` Pat Thoyts [this message]
2009-04-03 23:16     ` Johannes Schindelin
2009-04-03 23:42       ` [msysGit] " Pat Thoyts
2009-04-04  5:16     ` Marius Storm-Olsen
2009-04-04  6:35       ` [msysGit] " Johannes Sixt
2009-04-05 18:43         ` Marius Storm-Olsen
2009-04-03 15:01 ` Johannes Schindelin
2009-04-03 15:50   ` Janos Laube

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=a5b261830904031412o60b7eb4fv7e25a2ca4f89fe60@mail.gmail.com \
    --to=patthoyts@googlemail.com \
    --cc=git@vger.kernel.org \
    --cc=marius@trolltech.com \
    --cc=msysgit@googlegroups.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 NNTP newsgroup(s).