<body><div id="__MailbirdStyleContent" style="font-size: 10pt;font-family: Arial;color: #000000;text-align: left" dir="ltr">
Actually, the algorithm in #nanosecondsToRunHighRes: accounts for that, but variation can be significant...<div><br></div><div>Thus, I would not recommend using #nanosecondsToRun: but use #bench for that instead.</div><div><br></div><div>Best,</div><div>Marcel</div><div class="mb_sig"></div><blockquote class='history_container' type='cite' style='border-left-style:solid;border-width:1px; margin-top:20px; margin-left:0px;padding-left:10px;'>
<p style='color: #AAAAAA; margin-top: 10px;'>Am 22.02.2023 11:41:02 schrieb Marcel Taeumel <marcel.taeumel@hpi.de>:</p><div style='font-family:Arial,Helvetica,sans-serif'><div id="__MailbirdStyleContent" style="font-size: 10pt;font-family: Arial;color: #000000;text-align: left" dir="ltr">
FYI: It takes a notable amount of nanoseconds to even fetch the high-res clock value ...<div><br></div><div><div><span style="font-size: 13.3333px">[ String new ] bench</span></div><div><span style="font-size: 13.3333px">" '72,900,000 per second. 13.7 nanoseconds per run. 8.29834 % GC time.' "</span></div></div><div><br></div><div>Best,</div><div>Marcel</div><div class="mb_sig"></div><blockquote class='history_container' type='cite' style='border-left-style:solid;border-width:1px; margin-top:20px; margin-left:0px;padding-left:10px;'>
<p style='color: #AAAAAA; margin-top: 10px;'>Am 22.02.2023 11:39:44 schrieb Marcel Taeumel <marcel.taeumel@hpi.de>:</p><div style='font-family:Arial,Helvetica,sans-serif'><div id="__MailbirdStyleContent" style="font-size: 10pt;font-family: Arial;color: #000000;text-align: left" dir="ltr">
<div><span style="font-size: 13.3333px">Time startUp: true.</span></div><div><span style="font-size: 13.3333px">Time useHighResClockForTiming: true.</span></div><div><span style="font-size: 13.3333px">Time nanosecondsToRun: [ String new ]." 3193 "</span></div><div><br></div><div class="mb_sig"></div><blockquote class='history_container' type='cite' style='border-left-style:solid;border-width:1px; margin-top:20px; margin-left:0px;padding-left:10px;'>
<p style='color: #AAAAAA; margin-top: 10px;'>Am 22.02.2023 11:27:55 schrieb commits@source.squeak.org <commits@source.squeak.org>:</p><div style='font-family:Arial,Helvetica,sans-serif'>Marcel Taeumel uploaded a new version of Chronology-Core to project Squeak 6.0:<br>http://source.squeak.org/squeak60/Chronology-Core-mt.81.mcz<br><br>==================== Summary ====================<br><br>Name: Chronology-Core-mt.81<br>Author: mt<br>Time: 22 February 2023, 11:27:44.882528 am<br>UUID: e4a5b396-8917-7f46-a6c7-a6961ff588af<br>Ancestors: Chronology-Core-ct.80<br><br>Fixes #highResClock usage by resetting the estimated #highResClockTicksPerMillisecond on system start-up. The preference #useHighResClockForTiming works now as well.<br><br>=============== Diff against Chronology-Core-ct.80 ===============<br><br>Item was changed:<br> ----- Method: Time class>>startUp: (in category 'system startup') -----<br> startUp: resuming<br> <br> resuming ifTrue: [<br>+ LastClockTick := 0.<br>+ HighResClockTicksPerMillisecond := 0 ]!<br>- LastClockTick := 0 ]!<br><br>Item was added:<br>+ ----- Method: Time class>>useHighResClockForTiming: (in category 'preferences') -----<br>+ useHighResClockForTiming: booleanOrNil<br>+ <br>+ UseHighResClockForTiming := booleanOrNil.!<br><br><br></div></blockquote>
</div></div></blockquote>
</div></div></blockquote>
</div></body>