diff options
author | Vincent Ambo <mail@tazj.in> | 2022-12-11T12·16+0300 |
---|---|---|
committer | tazjin <tazjin@tvl.su> | 2022-12-21T22·21+0000 |
commit | bf286a54bc2ac5eeb78c3d5c5ae66e9af24d74d4 (patch) | |
tree | b2e6b72907e537da775c27d6b9fe95b817abd387 /ops/journaldriver/src | |
parent | 8b3d03db92c92fac09c92b55f946ae81299491ae (diff) |
refactor(tvix/eval): add a LightSpan type for lighter span tracking r/5457
This type carries the information required for calculating a span (i.e. the chunk and offset), instead of the span itself. The span is then only calculated in cases where it is required (when throwing errors). This reduces the eval time for `builtins.length (builtins.attrNames (import <nixpkgs> {}))` by *one third*! The data structure in chunks that carries span information reduces in-memory size by trading off the speed of retrieving span information. This is because the span information is only actually required when throwing errors (or emitting warnings). However, somewhere along the way we grew a dependency on carrying span information in thunks (for correctly reporting error chains). Hitting the code paths for span retrieval was expensive, and carrying the spans in a different way would still be less cache-efficient. This change is the best tradeoff I could come up with. Refs: b/229. Change-Id: I27d4c4b5c5f9be90ac47f2db61941e123a78a77b Reviewed-on: https://cl.tvl.fyi/c/depot/+/7558 Reviewed-by: grfn <grfn@gws.fyi> Tested-by: BuildkiteCI
Diffstat (limited to 'ops/journaldriver/src')
0 files changed, 0 insertions, 0 deletions