Path: utzoo!utgpu!news-server.csri.toronto.edu!mailrus!wuarchive!usc!snorkelwacker!bloom-beacon!eru!luth!sunic!mcsun!ukc!harrier.ukc.ac.uk!rlh2
From: rlh2@ukc.ac.uk (Richard Hesketh)
Newsgroups: comp.windows.x
Subject: Re: Performance (also an R5 Toolkit Wish)
Message-ID: <5354@harrier.ukc.ac.uk>
Date: 28 Aug 90 08:58:19 GMT
References: <1141@phcisa.UUCP>
Reply-To: rlh2@ukc.ac.uk (Richard Hesketh)
Organization: Computing Lab, University of Kent at Canterbury, UK.
Lines: 27

In article <1141@phcisa.UUCP>, frans@phcisa.UUCP (Francois Staes) writes: 
|> Can smoebody tell me where I can find such a fast memory allocator ?
|> Can I simply use the malloc.c file as distributed with e.g. emacs ?

Yes this seems to work just fine.  Infact it is *extremely* quicker when a
large number of widgets need to be created.   I have just tried this with
an application that creates >100 widgets and here's the two "time"s for
SPARCstations:

With libc malloc:     16.9u 1.2s 0:23 77% 0+2112k 61+0io 51pf+0w
With GNU malloc:      6.4u 1.5s 0:15 52% 0+2456k 4+0io 130pf+0w

This is a very rough comparison but shows what I have found in practice,
the GNU malloc is over twice as quick for widget widget creation
than the libc malloc.  It has reduced my applications start up time from
28 seconds to 11 seconds (on a SPARC).

Here comes the wish then ... how about a malloc written just for Xt and included
in the R5 release?  I wouldn't want to say "just use the GNU malloc" because
of copyright restrictions.

--
Richard Hesketh   :   @nsfnet-relay.ac.uk:rlh2@ukc.ac.uk
		  :   rlh2@ukc.ac.uk    ..!mcsun!ukc!rlh2
---                                               
Computing Lab., University of Kent at Canterbury,
Canterbury, Kent, CT2 7NF, United Kingdom.    Tel: +44 227 764000 ext 7620/3682