Skip to content
Snippets Groups Projects
Select Git revision
  • bd6e56448ef31e1275d30f4ed51c5796da0c5940
  • master default protected
  • 9.0
  • 8.0
  • nt-tools
  • 7.8
  • 7.6
  • 7.4
  • 7.2
  • 7.0
  • 0.6
  • rosuav/latex-markdown-renderer
  • rxnpatch/rxnpatch
  • marcus/gobject-introspection
  • rxnpatch/8.0
  • rosuav/pre-listening-ports
  • rosuav/async-annotations
  • rosuav/pgsql-ssl
  • rxnpatch/rxnpatch-broken/2023-10-06T094250
  • grubba/fdlib
  • grubba/wip/sakura/8.0
  • v8.0.2018
  • v8.0.2016
  • v8.0.2014
  • v8.0.2012
  • v8.0.2008
  • v8.0.2006
  • v8.0.2004
  • v8.0.2002
  • v8.0.2000
  • v8.0.1998
  • v8.0.1996
  • v8.0.1994
  • v8.0.1992
  • v8.0.1990
  • v8.0.1988
  • v8.0.1986
  • rxnpatch/clusters/8.0/2025-04-29T124414
  • rxnpatch/2025-04-29T124414
  • v8.0.1984
  • v8.0.1982
41 results

main.c

Blame
    • Henrik (Grubba) Grubbström's avatar
      89d10f35
      Runtime: Tune malloc(3C) in glibc. Alleviates [bug 6045]. · 89d10f35
      Henrik (Grubba) Grubbström authored
      Malloc(3C) in glibc defaults to having one pool (aka arena) of memory
      per thread. This means that by default memory released by one thread
      will not be reused by another thread. This in turn can cause a "pumping"
      effect where one thread temporarily may use a lot of memory, which
      causes that thread's arena to grow. If the same code is run again later,
      but by a different thread, that threads arena will grow even though
      there's plenty of free memory in the old arena. This means that there's
      a multiplication effect by the number of active threads.
      
      This implements the suggested work-around from the similar bug at
      http://sourceware.org/bugzilla/show_bug.cgi?id=11261
      89d10f35
      History
      Runtime: Tune malloc(3C) in glibc. Alleviates [bug 6045].
      Henrik (Grubba) Grubbström authored
      Malloc(3C) in glibc defaults to having one pool (aka arena) of memory
      per thread. This means that by default memory released by one thread
      will not be reused by another thread. This in turn can cause a "pumping"
      effect where one thread temporarily may use a lot of memory, which
      causes that thread's arena to grow. If the same code is run again later,
      but by a different thread, that threads arena will grow even though
      there's plenty of free memory in the old arena. This means that there's
      a multiplication effect by the number of active threads.
      
      This implements the suggested work-around from the similar bug at
      http://sourceware.org/bugzilla/show_bug.cgi?id=11261
    list-obj-sizes.awk 1.04 KiB