You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 253b5a8
Browse filesBrowse the repository at this point in the historyBrowse files
Benchmark trigonometry against precision, and stop discarding the allocations (#167) (#850)
Both halves of what #167 asked for.
CommonFunctionsInterVersion had no trigonometric case at any precision.
EvalTrig and EvalTrigPrecise evaluate sin(1) + cos(1) + tan(1) at the default
hundred digits and at five hundred. Both build their nodes on every call: an
Entity caches its own Evaled, so the obvious form of this benchmark measures a
dictionary lookup rather than any arithmetic.
Which is what EvalEasy has been measuring since that cache landed, and why it
reads two nanoseconds. Left as it is so the column history stays comparable,
with the trap written down.
The class has carried [MemoryDiagnoser] all along, so the allocation figure was
collected on every run and then dropped, because Program.cs asked for Mean,
Error and StdDev and nothing else. It now asks for Allocated too.
0 commit comments