From: Hans Hagen <pragma@wxs.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: XeConTeXt bug report I: strange benchmark
Date: Tue, 12 May 2009 17:20:12 +0200 [thread overview]
Message-ID: <4A0993AC.4000707@wxs.nl> (raw)
In-Reply-To: <68bfdc900905120810m38a20dcaoee39d2c23d07368a@mail.gmail.com>
Yue Wang wrote:
> loading 6 fonts, each fonts will be scanned for 3 times. so there are
> 18 searching. 12 of them are fc searches, and these are quite slow.
if so, then this fc mechanism is pretty messed up as it's just a hash
lookup which cna be fast
also, it does not explain why simple plain definitions also have a
suffix and/or name lookup problem so you'd better make sure that that is
fixed too (if only because we cannot be sure of users always using
filenames)
in the meantime i'll add some lookup caching in the xetex specific
context code (costs a bit of extra hash mem but lets not bother about that)
Hans
-----------------------------------------------------------------
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-05-12 15:20 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-12 5:01 Yue Wang
2009-05-12 9:02 ` Yue Wang
2009-05-12 9:09 ` Yue Wang
2009-05-12 9:30 ` Hans Hagen
2009-05-12 9:59 ` Yue Wang
2009-05-12 10:04 ` Yue Wang
2009-05-12 10:06 ` Hans Hagen
[not found] ` <4A094C71.3040503@elvenkind.com>
2009-05-12 11:02 ` Hans Hagen
2009-05-12 11:26 ` Taco Hoekwater
2009-05-12 11:33 ` Yue Wang
2009-05-12 11:52 ` Taco Hoekwater
2009-05-12 11:57 ` Hans Hagen
2009-05-12 12:01 ` Yue Wang
2009-05-12 12:21 ` Hans Hagen
2009-05-12 12:26 ` Taco Hoekwater
2009-05-12 12:31 ` Yue Wang
2009-05-12 11:09 ` Yue Wang
2009-05-12 11:37 ` Hans Hagen
2009-05-12 12:26 ` Yue Wang
2009-05-12 12:54 ` Hans Hagen
2009-05-12 13:59 ` Yue Wang
2009-05-12 14:11 ` Yue Wang
2009-05-12 15:02 ` Hans Hagen
2009-05-12 15:12 ` Yue Wang
2009-05-12 15:22 ` Hans Hagen
2009-05-12 15:45 ` Yue Wang
2009-05-13 4:38 ` Yue Wang
2009-05-13 7:49 ` Yue Wang
2009-05-13 8:28 ` Hans Hagen
2009-05-12 15:45 ` Hans Hagen
2009-05-12 14:50 ` Hans Hagen
2009-05-12 15:10 ` Yue Wang
2009-05-12 15:14 ` Taco Hoekwater
2009-05-12 15:41 ` Hans Hagen
2009-05-12 15:49 ` Yue Wang
2009-05-12 15:20 ` Hans Hagen [this message]
2009-05-12 15:50 ` Hans Hagen
2009-05-13 8:59 ` Mojca Miklavec
2009-05-13 9:55 ` Mojca Miklavec
2009-05-13 11:12 ` Hans Hagen
2009-05-13 11:17 ` Hans Hagen
2009-05-13 10:02 ` Wolfgang Schuster
2009-05-13 10:17 ` Mojca Miklavec
2009-05-13 10:41 ` Wolfgang Schuster
2009-05-13 11:12 ` Mojca Miklavec
2009-05-13 11:28 ` Wolfgang Schuster
2009-05-13 12:48 ` Thomas A. Schmitz
2009-05-13 12:26 ` Yue Wang
2009-05-13 12:59 ` Hans Hagen
2009-05-13 13:25 ` Wolfgang Schuster
2009-05-12 11:01 ` Wolfgang Schuster
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=4A0993AC.4000707@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).