From: Hans Hagen <j.hagen@xs4all.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>,
Mojca Miklavec <mojca.miklavec.lists@gmail.com>
Subject: Re: TeX Live 2019: attempt to call a nil value (upvalue 'isfile')
Date: Fri, 1 Mar 2019 12:41:34 +0100 [thread overview]
Message-ID: <257b6a14-05c8-96f8-c84d-eaec70077b48@xs4all.nl> (raw)
In-Reply-To: <CALBOmsbV4oiR-_nXuDK7UHVppYq8VOsKBn1yvXr609_KuJ3b5A@mail.gmail.com>
On 3/1/2019 12:01 PM, Mojca Miklavec wrote:
> On Fri, 1 Mar 2019 at 08:50, luigi scarso wrote:
>>
>> $> context luatex
>> mkiv lua stats > used platform: linux-64, type: unix, binary subtree: texmf-linux-64
>> mkiv lua stats > used engine: luatex version 1.1 with functionality level 7088, banner: this is luatex, version 1.10.0 (tex live 2019)
>> mkiv lua stats > control sequences: 53180 of 65536 + 100000
>> mkiv lua stats > lua properties: engine: lua 5.3, used memory: 441 MB (ctx: 437 MB), hash chars: min(64,40), symbol mask: utf (τεχ)
>> mkiv lua stats > runtime: 21.608 seconds, 294 processed pages, 294 shipped pages, 13.606 pages/second
>> system | total runtime: 47.547 seconds
>
> OK, strange. It works for me in TeX Live as well after I installed the
> missing dejavu fonts. I didn't imagine that it would break with such a
> strange error when a font is missing though.
>
>> ( forget the time, it's a zero-optimized binary (fast to compile))
>
> It takes even longer for me with the binary from the distribution.
On the mac, is that one run?
With luatex 1.10 (mingw 64 version), when i delete the tuc file so with
multiple runs to get the cross ref and lists right, I get:
mkiv lua stats > runtime: 13.676 seconds, 294 processed pages, 294
shipped pages, 21.498 pages/second
system | total runtime: 67.472 seconds
After that, single runs take around 13 seconds:
mkiv lua stats > runtime: 13.227 seconds, 294 processed pages, 294
shipped pages, 22.227 pages/second
so, so, on my laptop (which for sure is slower than yours) a 21 pps rate
is normal
Hans
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | www.pragma-ade.nl | 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://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___________________________________________________________________________________
prev parent reply other threads:[~2019-03-01 11:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-28 23:14 Henri Menke
2019-02-28 23:17 ` Henri Menke
2019-02-28 23:20 ` luigi scarso
2019-03-01 6:39 ` Mojca Miklavec
2019-03-01 7:15 ` Mojca Miklavec
2019-03-01 7:50 ` luigi scarso
2019-03-01 11:01 ` Mojca Miklavec
2019-03-01 11:11 ` luigi scarso
2019-03-01 11:41 ` Hans Hagen [this message]
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=257b6a14-05c8-96f8-c84d-eaec70077b48@xs4all.nl \
--to=j.hagen@xs4all.nl \
--cc=mojca.miklavec.lists@gmail.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).