<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">Hi,<div><br><div><div>Le 27 juil. 2017 at 17:26, George N. White III <<a href="mailto:gnwiii@gmail.com">gnwiii@gmail.com</a>> wrote :</div><br class="Apple-interchange-newline"><blockquote type="cite"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On 27 July 2017 at 09:44, jfbu <span dir="ltr"><<a href="mailto:jfbu@free.fr" target="_blank">jfbu@free.fr</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">[...] </blockquote><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
Hence now no \numexpr, only Knuth tex<br>
<br>
When I do<br>
<br>
time tex testspeed.tex<br>
<br>
I consistently get on my iMac 10.9.5:<br>
<br>
- with TL2015: about 1.62s (last digit non-significant)<br>
<br>
- with TL2017: about 2.18s (idem)<br>
<br>
Thus, it appears, but somehow I had overlooked it so far,<br>
that darwinlegacy tex (et al.) is at least 33% slower on TL2017<br>
than formerly<br>
<br></blockquote><div><br></div><div>I have iMac 10.11.6 with 4 TeX Live systems (current macports, TL2015--TL2017) and </div><div>checkX.sh scripts that format the same set of basic files on each.</div><div><br></div><div>After several iterations, times are reasonably stable. The last run gave:</div><div><br></div><div><p class="gmail-p1"> macports TL2015 TL2016 TL2017</p><p class="gmail-p1"><span class="gmail-s1"><font face="monospace, monospace">real<span class="gmail-Apple-tab-span"> </span> 0m2.628s </font></span><span style="font-family:monospace,monospace">0m3.901s </span><span style="font-family:monospace,monospace">0m4.610s </span><span style="font-family:monospace,monospace">0m4.587s</span></p><p class="gmail-p1"><span class="gmail-s1"><font face="monospace, monospace">user <span class="gmail-Apple-tab-span"> </span>0m2.156s </font></span><span style="font-family:monospace,monospace">0m3.352s </span><span style="font-family:monospace,monospace">0m4.085s </span><span style="font-family:monospace,monospace">0m3.996s </span></p><p class="gmail-p1"><font face="monospace, monospace"><span class="gmail-s1">sys<span class="gmail-Apple-tab-span"> </span> 0m0.313s </span>0m0.343s 0m0.368s 0m0.378s</font></p><p class="gmail-p1"><br></p><p class="gmail-p1">There is a big gain to had from compiling locally over the generic TL builds, and not much change from TL2016 to TL2017.</p></div></div></div></div></blockquote><br></div><div>This is very interesting thanks.</div><div><br></div><div>It dispels somewhat my obsession about the specificity of darwinlegacy.</div><div><br></div><div>The difference with the macports binaries is impressive and unexpected to me.</div><div><br></div><div>And the change from TL2015 to TL2017 is at least 10% which again</div><div>surprises me. However it could be inside the margin of fluctuation</div><div>from run to run perhaps.</div><div><br></div><div>I am very much interested now into compiling locally, but I will be off internet</div><div>for a while so I will have to think by myself how to achieve that after having</div><div>rsync'ed the TeXLive sources, and thinking by myself might prove hard.</div><div><br></div><div>Best,</div><div><br></div><div>Jean-Francois</div><br></div></body></html>