ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Taco Hoekwater <taco@elvenkind.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: XeConTeXt bug report I: strange benchmark
Date: Tue, 12 May 2009 13:26:08 +0200	[thread overview]
Message-ID: <4A095CD0.5060405@elvenkind.com> (raw)
In-Reply-To: <4A09574C.6050201@wxs.nl>

Hans Hagen wrote:
>  > Taco Hoekwater wrote:
>>
>> Hans Hagen wrote:
>>> anyway .. i cannot comment on runtimes as xetex on my windows box runs
>>> too slow (caching issue) and all examples are slow, no matter how i
>>> specify fonts so i will not look into the code till that gets fixed 
>>> first
>>
>> The example with the typescript seems logical to me: a typescript does
>> much work beforehand, so I assume SimSum is loaded multiple times.
>>
>> I am trying the AdobeSong example as we speak, there surely seems
>> something wrong there.
> 
> let's start with saying that I have no intention to optimize mkii for 
> xetex as we decided some time ago (at the context meeting) that we would 

For educational purposes: whether you have

   \definefont[a][file:AdobeSongLight-Std]
or
   \definefont[a][file:AdobeSongLight-Std.otf]

makes no difference to context at all.

The first makes \a expand into (simplified)

  \font\internala="[AdobeSongLight-Std]" at 12pt\internala

the second into

  \font\internala="[AdobeSongLight-Std.otf]" at 12pt\internala

but there are no other macro expansion changes at all. You can test
this yourself by making two alternative files an adding \loggingall
to them, then compare the two logs using diff.

As to the reason why one of the two is much slower than the other:
I do not know for sure, but I suspect that XeTeX does not cache
the (some of) the internals results of font file assignments with
explicit extensions. The speed difference is most certainly *not*
caused by anything the context macros do.

Best wishes,
Taco

PS As to why \definefont is itself slower than \font: it does not
actually define a font \a at a specific size. Instead it defines a
macro \a that defines and then selects a font with an internal,
temporary name, using the local font size etc.









___________________________________________________________________________________
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
___________________________________________________________________________________


  reply	other threads:[~2009-05-12 11:26 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 [this message]
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=4A095CD0.5060405@elvenkind.com \
    --to=taco@elvenkind.com \
    --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).