Commit Graph

11 Commits

Author SHA1 Message Date
Miguel M f420690041 pure python for comparison 2023-02-28 21:20:06 +00:00
Miguel M 39cfb20f13 touchups 2023-02-28 21:19:50 +00:00
Miguel M e85346e916 could have used a map instead of running twice, preparing to make that
change
2023-02-26 18:07:25 +00:00
Miguel M b899ddd63a Final commit, in principle.
Got things running at about ~1ns per iteration, seems good enough.
Adopted a linear strategy to evaluating the bytecode, rather than a
recursive or even imperative evaluation strategy; this also lets me
elide the offsets and store the bytecode in half the size. Looking
forward to finding out that formulas are evaluated wrongly, but couldn't
find a counterexample. Also restructured things a bit to avoid multiple
alocations when evaluating by this strategy.
2023-02-24 19:41:51 +00:00
Miguel M 3a6c511ed5 optimized bottlenecks based on benchmarks. fast now 2023-02-24 18:23:37 +00:00
Miguel M 4a579cd2fd added tests, produced a flamegraph. VM seems to be the bottleneck 2023-02-24 14:50:26 +00:00
Miguel M 2dd7160fba Undid parallelization changes, fairly sure it degraded perf
This reverts commit 5a296819aedfcfd9a318df524d5ba3a5091f3a69.
2023-02-23 18:29:05 +00:00
Miguel M deb080d29d parallelized search; not sure it is efficient 2023-02-23 18:26:58 +00:00
Miguel M 9bd4dcf010 first implementation of bounds search 2023-02-23 02:07:40 +00:00
Miguel M a5ea324114 integer math where possible 2023-02-22 17:45:13 +00:00
Miguel M 179152a278 vm working 2023-02-22 16:58:37 +00:00