aboutsummaryrefslogtreecommitdiffstats
path: root/docs/research/098-link-security.md
diff options
context:
space:
mode:
authoreunhhu <[email protected]>2026-10-08 13:08:06 +0100
committereunhhu <[email protected]>2026-10-08 13:08:06 +0100
commit43815a41bfab2f561bf69ecb0bd5de75bef3678a (patch)
treedf9ad5dbac5276ed0c4d62f3620e78a1d901ae4a /docs/research/098-link-security.md
parentee4e1510819a916bf84cd4b560b05f520d32e86b (diff)
downloadpure-43815a41bfab2f561bf69ecb0bd5de75bef3678a.tar.gz
pure-43815a41bfab2f561bf69ecb0bd5de75bef3678a.zip
Research 132 (no code): where the batch executor's cost sits (an element's passes through memory; a batch's fixed cost about 6,500 instructions, 1 us, measured by 1024 against 256 lanes: fewer lanes are slower, so 024's L1 sizing was the wrong lever; a candidate's tail about 250), what the database literature measured of the same shape (X100, Kersten 2018's cycles and instructions a tuple, Sompolski 2011, Gubner 2017's in-register aggregation, Photon, Ertl and Gregg), the ways judged by the philosophy (a batch program made once at load; register tiles with threaded dispatch as the one general way past the floor; a table of fused operations and AOT C out), and the deciding experiment with its bar first (three bodies in tiles of 4, 8, 16: within 1.3x the compiled code's cycles an element, or it is not the answer); 041 lanes data
Diffstat (limited to 'docs/research/098-link-security.md')
0 files changed, 0 insertions, 0 deletions