Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sun-barr!apple!keith
From: keith@Apple.COM (Keith Rollin)
Newsgroups: comp.sys.mac.programmer
Subject: Re: Explanation for incredibly slow NewPtr(and NewHandle) on ci and fx
Message-ID: <46711@apple.Apple.COM>
Date: 19 Nov 90 21:48:18 GMT
References: <649@nih-csl.nih.gov> <9_|^6Z_@rpi.edu>
Organization: Apple Computer Inc., Cupertino, CA
Lines: 27

In article <9_|^6Z_@rpi.edu> Garance_Drosehn@mts.rpi.edu (Garance Drosehn) writes:
>In article <649@nih-csl.nih.gov> 
>           wayne@helix.nih.gov (Wayne Rasband) writes:
>   ...(majority of article deleted)...
>> 
>> /          ci     cx    ci/cx      MMINIT ci   ci/MMINIT ci*/
>> /* totals  1797   222   8:1        192         9.4:1       */
>
>With differences like that, I imagine this MMINIT (wherever it is) will be 
>very popular!

True, but the Memory Manager bug affects only certain applications.
Most applications aren't affected. As near as I can tell, applications
that either allocate a large number of non-relocatable blocks of memory
with NewPtr or that don't call MoreMasters enough when dealing with
thousands of handles (and hence make implicit NewPtr calls in the
middle of their programs) are affected. Almost no other applications
are impacted (for example, my 26 minute compile of an application under
MPW, which is a very Memory Manager intensive program, still takes 26
minutes).

-- 
------------------------------------------------------------------------------
Keith Rollin  ---  Apple Computer, Inc.  ---  Developer Technical Support
INTERNET: keith@apple.com
    UUCP: {decwrl, hoptoad, nsc, sun, amdahl}!apple!keith
"Argue for your Apple, and sure enough, it's yours" - Keith Rollin, Contusions