<@UB2J9BQA0>: nice work on <https://gist.github.co...
# development
@hundreds-father-404: nice work on https://gist.github.com/Eric-Arellano/defca7d864a9f3939448964beea618d4 . i expect that
is lying to you a bit, because it isn't recursive (see https://docs.python.org/3/library/sys.html#sys.getsizeof), but that measuring recursively is challenging here (because things like TransitiveHydratedTarget intentionally structure share, and would lie to a naive recursive size calculation).
might help there.
having said that, it's pretty clear that eliminating all cases where we hold FileContent in memory seems like the big one.
stdout/stderr are likely to be problematic as well... we discussed making those lazy on
initially, but went for eager in the end.
some of this might boil down to the rust/python boundary, in that when an
rule "lifts" a "large" type to be fed to a python
, it should avoid actually persisting that in the
aaaaaand going to bed
❤️ 1
thank you for looking at this!
... hm. having said that. all of the things in the
map are
held inside the NodeKey/NodeResult enums. so that's not really very helpful.
but still going to bed.
😴 1