From: Hans Hagen <pragma@wxs.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Possible memory leak?
Date: Mon, 02 Feb 2009 09:47:52 +0100 [thread overview]
Message-ID: <4986B338.6080903@wxs.nl> (raw)
In-Reply-To: <68bfdc900902012035s3aee016eo34b70f94d75b112c@mail.gmail.com>
Yue Wang wrote:
>> also, mem consumption reported is a bit of a lie because lua seems to
>> allocates double of what it needed with each increment but not always use it
>>
>> otf fonts are already quite packed in mkiv (i'm considering adding an option
>> to mtx-font to precache fonts but i'm not sure if it's worth the trouble
>>
>> is mem consumption less a second run?
>
> Yes, dramatically less. with 4 chinese fonts loaded (I use zhfonts.tex
> for testing), MKIV consumes 300-400MB.
on my machine running mk with a fresh cache gives the same lua mem usage
as with filled cache, however a fresh run tops at 1 meg while a filled
run tops ar 500 (windows vista); that document uses several cjk fonts
(relatively large due to many glyphs) and script fonts (some arabic and
zapfino as well as cambria math which are much larger fonts due to many
features
mkiv lua stats : loaded fonts - adobesongstd-light:otf
arabtype:ttf c:/windows/fonts/cambria:ttc htfs:ttf htsong:ttf ko
eieletters:afm lmex10:tfm lmmi10:tfm lmmib10:tfm lmmono10-regular:otf
lmmonoltcond10-regular:otf lmroman10-italic:otf lmroman10-regu
lar:otf lmroman12-regular:otf lmsans10-regular:otf lmsy10:tfm
lmtypewriter10-regular:otf msam10:tfm msbm10:tfm palatinoltarabic-regu
lar:ttf rm-lmbx10:tfm rm-lmr10:tfm rm-lmr12:tfm rm-lmr8:tfm
rm-lmtt10:tfm scheherazaderegot:ttf texnansi-lt55484:afm texnansi-lt5548
5:afm texnansi-lt55488:afm texnansi-lt55507:afm zapfinoextraltpro:otf
mkiv lua stats : current memory usage - 361 MB (ctx: 370 MB)
(keep in mind that at some point luatex has to load the glyph shapes and
pass them to the pdf file so there will always be otf/pfb loading at the
end of a run)
as taco mentioned, real memory usage for a fresh run is probably
somewhat lower due to fragmentation
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com
| www.pragma-pod.nl
-----------------------------------------------------------------
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://tex.aanhet.net
archive : https://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2009-02-02 8:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-01 14:44 Yue Wang
2009-02-01 15:03 ` Hans Hagen
2009-02-02 4:35 ` Yue Wang
2009-02-02 8:47 ` Hans Hagen [this message]
2009-02-02 9:13 ` Yue Wang
2009-02-02 22:14 ` Taco Hoekwater
2009-02-01 15:47 ` Taco Hoekwater
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=4986B338.6080903@wxs.nl \
--to=pragma@wxs.nl \
--cc=ntg-context@ntg.nl \
/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).