From: Yue Wang <yuleopen@gmail.com>
To: Jonathan Kew <jonathan_kew@sil.org>,
mailing list for ConTeXt users <ntg-context@ntg.nl>,
Jin-Hwan Cho <chofchof@ktug.or.kr>
Subject: Re: XeConTeXt bug report I: strange benchmark
Date: Tue, 12 May 2009 17:02:52 +0800 [thread overview]
Message-ID: <68bfdc900905120202o2dc78751q3c87ae62b80e1795@mail.gmail.com> (raw)
In-Reply-To: <68bfdc900905112201w66e00fb3q6213887b41d16bbc@mail.gmail.com>
Hi:
update: change the second example, remove the ".otf" suffix , and
texexec --xtx gives:
TeXExec | runtime: 5.766
Obviously, this is a parsing bug in ConTeXt.
I doubt the reason to the third one is the same.
Yue Wang
2009/5/12 Yue Wang <yuleopen@gmail.com>:
> Hi, Hans and Jonathan:
>
> I made some testing samples in ConTeXt to test XeTeX. but the result
> is quite strange. All benchmark are get from the second run:
>
> Sample 1:
>
> \definefont[a][file:SimSun]
> \starttext
> \dorecurse{10000}{ hello {\a 你好}}
> \stoptext
>
> And here is the result:
>
> XeTeX: TeXExec | runtime: 7.25
> LuaTeX: MTXrun | total runtime: 6.719
>
> This is considerablly ok. So we can say that the font switching is pretty fast.
>
> Sample 2:
>
> \definefont[a][file:AdobeSongStd-Light.otf]
> \starttext
> \dorecurse{10000}{ hello {\a 你好}}
> \stoptext
>
> XeTeX: TeXExec | runtime: 63.65
> LuaTeX: MTXrun | total runtime: 8.156
>
> Here I only change the font from SimSun to Adobe Song (the two fonts
> are almost at the same sice [~10M]).
> But the xetex result is very differt from the previous run. it
> consumes one minute to compile the file.
>
>
> Sample 3:
>
>
> \starttypescript[serif] [myzhfont]
> \definefontsynonym [Serif] [file:SimSun]
> \definefontsynonym [SerifBold] [file:SimSun]
> \definefontsynonym [SerifItalic] [file:SimSun]
> \definefontsynonym [SerifBoldItalic] [file:SimSun]
> \stoptypescript
>
> \starttypescript[sans] [myzhfont]
> \definefontsynonym [Sans] [file:SimSun]
> \definefontsynonym [SansBold] [file:SimSun]
> \definefontsynonym [SansItalic] [file:SimSun]
> \definefontsynonym [SansBoldItalic] [file:SimSun]
> \stoptypescript
>
> \starttypescript[mono] [myzhfont]
> \definefontsynonym [Mono] [file:SimSun]
> \definefontsynonym [MonoBold] [file:SimSun]
> \definefontsynonym [MonoItalic] [file:SimSun]
> \definefontsynonym [MonoBoldItalic] [file:SimSun]
> \stoptypescript
>
> \definetypeface [myzhfont] [rm] [serif][myzhfont] [default]
> \definetypeface [myzhfont] [ss] [sans] [myzhfont] [default]
> \definetypeface [myzhfont] [tt] [mono] [myzhfont] [default]
>
> \def\a{\myzhfont}
> \starttext
> \dorecurse{10000}{ hello {\a 你好}}
> \stoptext
>
> XeTeX: TeXExec | runtime: 64.797
> LuaTeX: MTXrun | total runtime: 10.797
>
> Here we use SimSun since in the first sample xetex can load simsun quite fast.
> However, in this time we define a typescript, and make all the styles
> fall into SimSun.
> Now xetex behaves quite strangely: it uses one minutes to compile this
> single document...
>
>
> So my question is
> - why loading otf is so slow?
> - is this a bug in context or in xetex? can it be fixed?
> - how can we make sample 3 (using typescript) run faster?
>
>
> Thanks.
>
> Yue Wang
>
___________________________________________________________________________________
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 9:02 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 [this message]
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
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=68bfdc900905120202o2dc78751q3c87ae62b80e1795@mail.gmail.com \
--to=yuleopen@gmail.com \
--cc=chofchof@ktug.or.kr \
--cc=jonathan_kew@sil.org \
--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).