Dear list, although I cannot find it now, I sent a message to the list describing that I suspected ConTeXt wasn’t as fast as it should on my computer. Here you have a minimal sample: \starttext \input knuth \stoptext It takes about 3.5 seconds total runtime to compile. Is this the standard required time? Actually what I wonder is why the compilation requires three runs to output the final document. Many thanks for your help, Pablo -- http://www.ousia.tk
Am 12.08.2013 um 18:40 schrieb Pablo Rodríguez
Dear list,
although I cannot find it now, I sent a message to the list describing that I suspected ConTeXt wasn’t as fast as it should on my computer.
Here you have a minimal sample:
\starttext \input knuth \stoptext
It takes about 3.5 seconds total runtime to compile. Is this the standard required time?
Your minimal example takes for me on the first 1.8 (terminal) to 2 seconds (editor) and each consecutive run about 0.6 seconds.
Actually what I wonder is why the compilation requires three runs to output the final document.
When you process a new document the first time context takes three runs to store and read data in the temp files (references and roc etc. values). After this context takes in most cases only a single run unless references have changed (e.g. the reference is now on a new page) or new entries are written to the temp files (e.g. when you add a additional heading). Wolfgang
On 08/12/2013 07:20 PM, Wolfgang Schuster wrote:
Am 12.08.2013 um 18:40 schrieb Pablo Rodríguez
: [...] It takes about 3.5 seconds total runtime to compile. Is this the standard required time?
Your minimal example takes for me on the first 1.8 (terminal) to 2 seconds (editor) and each consecutive run about 0.6 seconds.
Many thanks for your reply, Wolfgang. So if I need three times for each compilation (since I use --purgeall), the time is fine, since my laptop is already some years old. Pablo -- http://www.ousia.tk
On Mon, 12 Aug 2013, Pablo Rodríguez wrote:
So if I need three times for each compilation (since I use --purgeall), the time is fine, since my laptop is already some years old.
Out of curiosity, why do you use --purgeall? ConTeXt only generates two auxillary files (.tuc and .log), so it is does not really clutter the current working directory (unlike LaTeX which generates some 10 different aux files). Aditya
On 08/12/2013 10:37 PM, Aditya Mahajan wrote:
On Mon, 12 Aug 2013, Pablo Rodríguez wrote:
So if I need three times for each compilation (since I use --purgeall), the time is fine, since my laptop is already some years old.
Out of curiosity, why do you use --purgeall? ConTeXt only generates two auxillary files (.tuc and .log), so it is does not really clutter the current working directory (unlike LaTeX which generates some 10 different aux files).
I thought ConTeXt could generate more auxiliary files than two. And using --purgeall I don’t have to remember to delete auxiliary files when the document is finished. But I guess I‘ll use --purgeall only when the document is finished. Pablo -- http://www.ousia.tk
On Mon, 12 Aug 2013, Pablo Rodríguez wrote:
On 08/12/2013 10:37 PM, Aditya Mahajan wrote:
On Mon, 12 Aug 2013, Pablo Rodríguez wrote:
So if I need three times for each compilation (since I use --purgeall), the time is fine, since my laptop is already some years old.
Out of curiosity, why do you use --purgeall? ConTeXt only generates two auxillary files (.tuc and .log), so it is does not really clutter the current working directory (unlike LaTeX which generates some 10 different aux files).
I thought ConTeXt could generate more auxiliary files than two.
In MkII ConTeXt used to generate more auxiliary files; in MkIV it only generates one (.tuc). The log file is a TeX feature that cannot be turned off (I think). If you use bibtex, then ConTeXt must also generate the .aux file (because that is hardwired into bibtex!) and bibtex then generates a bbl file. So, in the worst case, you end up with four extra files. Aditya
On 8/12/2013 11:23 PM, Pablo Rodríguez wrote:
On 08/12/2013 10:37 PM, Aditya Mahajan wrote:
On Mon, 12 Aug 2013, Pablo Rodríguez wrote:
So if I need three times for each compilation (since I use --purgeall), the time is fine, since my laptop is already some years old.
Out of curiosity, why do you use --purgeall? ConTeXt only generates two auxillary files (.tuc and .log), so it is does not really clutter the current working directory (unlike LaTeX which generates some 10 different aux files).
I thought ConTeXt could generate more auxiliary files than two.
And using --purgeall I don’t have to remember to delete auxiliary files when the document is finished.
But I guess I‘ll use --purgeall only when the document is finished.
or just --purge as it will keep the tuc file ----------------------------------------------------------------- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | voip: 087 875 68 74 | www.pragma-ade.com | www.pragma-pod.nl -----------------------------------------------------------------
On 8/12/2013 6:40 PM, Pablo Rodríguez wrote:
Dear list,
although I cannot find it now, I sent a message to the list describing that I suspected ConTeXt wasn’t as fast as it should on my computer.
Here you have a minimal sample:
\starttext \input knuth \stoptext
It takes about 3.5 seconds total runtime to compile. Is this the standard required time?
Actually what I wonder is why the compilation requires three runs to output the final document.
mkiv lua stats > runtime: 0.250 seconds system | total runtime: 0.422 luajittex: mkiv lua stats > runtime: 0.200 seconds system | total runtime: 0.360 Dell Laptop: i7-3840QM @ 2.8G / 16 GB / 256G SSD / windows 8 64 bit \starttext \dorecurse{1000}{test\page} \stoptext does 540 pages per second of course in practice it all depends on what features are used but 3.5 seconds is way off, unless you remake the format each run (coul dbe the case of your luatex doesn't match texlua Hans ----------------------------------------------------------------- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | voip: 087 875 68 74 | www.pragma-ade.com | www.pragma-pod.nl -----------------------------------------------------------------
On 08/12/2013 09:55 PM, Hans Hagen wrote:
On 8/12/2013 6:40 PM, Pablo Rodríguez wrote:
It takes about 3.5 seconds total runtime to compile. Is this the standard required time?
Actually what I wonder is why the compilation requires three runs to output the final document.
mkiv lua stats > runtime: 0.250 seconds system | total runtime: 0.422
luajittex:
mkiv lua stats > runtime: 0.200 seconds system | total runtime: 0.360
Dell Laptop: i7-3840QM @ 2.8G / 16 GB / 256G SSD / windows 8 64 bit
\starttext \dorecurse{1000}{test\page} \stoptext
does 540 pages per second
Many thanks for the reply, Hans. My system does 172.980 pages/second in the last run. My laptop is way older than yours (Genuine Intel(R) CPU T2050 @ 1.60GHz / 2GB RAM / Fedora 19). Pablo -- http://www.ousia.tk
participants (4)
-
Aditya Mahajan
-
Hans Hagen
-
Pablo Rodríguez
-
Wolfgang Schuster