[Bf-committers] need help on vgroup/mdisp allocation
ideasman42 at gmail.com
Thu May 12 00:31:02 CEST 2011
+1 for using jemalloc, for durian we used it for all systems + the
render farm & it saved a lot of ram.
for *nix we can LD_PRELOAD jemalloc, so no special requirements other
then starting blender from a shell script,
windows needs some investigation though.
One of the main things to decide is weather jemalloc replaces all
alloc's (as with LD_PRELOAD), or only MEM_* functions since this
changes how its linked/bundled.
How about make this a build option and give some time for platform
maintainers to support, then default to ON when its working well?
On Wed, May 11, 2011 at 9:47 PM, Tom M <letterrip at gmail.com> wrote:
> Of additional interest is that since firefox facebook has made a
> number of improvements
> On Wed, May 11, 2011 at 12:41 PM, Tom M <letterrip at gmail.com> wrote:
>> Here are some useful jemalloc links
>> On Wed, May 11, 2011 at 12:32 PM, joe <joeedh at gmail.com> wrote:
>>> Using jemalloc on all platforms might be the best approach, plugged
>>> into guardedalloc. Integrating something like mempool or memarena in
>>> CustomData is possible, but not ideal (given how much code it would
>>> affect, and how close we are to trunk integration).
>>> Bf-committers mailing list
>>> Bf-committers at blender.org
> Bf-committers mailing list
> Bf-committers at blender.org
More information about the Bf-committers