pedestal 2024-10-09

It took some experimentation, but the CVE checks are now re-enabled on CI builds.

๐ŸŽ‰ 2

;โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”ณโ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”ณโ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”“
;โ”ƒ             Expression             โ”ƒ    Mean   โ”ƒ     Var     โ”ƒ
;โ”ฃโ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ•‹โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ•‹โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”ซ
;โ”ƒ  (execute-static :small :map-tree) โ”ƒ  18.05 ยตs โ”ƒ ยฑ 258.02 ns โ”ƒ (fastest)
;โ”ƒ  (execute-static :small :sawtooth) โ”ƒ  21.48 ยตs โ”ƒ ยฑ 695.38 ns โ”ƒ
;โ”ƒ (execute-static :medium :map-tree) โ”ƒ 176.26 ยตs โ”ƒ   ยฑ 1.92 ยตs โ”ƒ
;โ”ƒ (execute-static :medium :sawtooth) โ”ƒ 202.23 ยตs โ”ƒ   ยฑ 4.14 ยตs โ”ƒ
;โ”ƒ  (execute-static :large :map-tree) โ”ƒ  16.99 ms โ”ƒ ยฑ 181.81 ยตs โ”ƒ
;โ”ƒ  (execute-static :large :sawtooth) โ”ƒ  19.56 ms โ”ƒ ยฑ 395.42 ยตs โ”ƒ (slowest)
;โ”—โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”ปโ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”ปโ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”›

Starting to optimize :sawtooth for static-only (no path params) routing tables. Already it is quick enough, in my opinion, to be the default router.

๐Ÿ‘ 3

i think that the defualt router should be the best on error report//dev experience, not the fastest

My only concern is that upgrades from 0.7 to 0.8 may see different behavior with Sawtooth than with prefix-tree, but you would only see that if there were route conflicts to begin with, and (assuming there are tests) you'll see the warnings and know something is up immediately, and can decide to remove conflicts or move back to :prefix-tree.

๐Ÿ‘ 1