https://pantsbuild.org/ logo
#pex
Title
r

rough-minister-58256

11/13/2019, 9:14 PM
this could support smarter app runtimes that could do things like bootstrap their own resources/deps/interpreters/etc or other interesting features
a

aloof-angle-91616

11/13/2019, 9:15 PM
yes, i’d really really like this to happen
r

rough-minister-58256

11/13/2019, 9:16 PM
to this end: I have heard lots of complaints of late about multi-second pex execution startup times from Twitter folks, I worry it’s gotten worse recently. that’d be a core problem to fix in both pex and any carry-forward.
a

aloof-angle-91616

11/13/2019, 9:17 PM
yes, that’s partially why i wanted to pursue the dehydrated solution within pex (i wanted a formal solution instead of throwaway scripts)
we can try to pair on this sometime this week or anytime in the future if you’d like
i also personally need to get more familiar with the pex bootstrap process and what the profile looks like when a pex is executed
h

hundreds-father-404

11/13/2019, 9:21 PM
Huh do you think any of this is that Pants no longer includes .pyc? When did the complaints start?
a

aloof-angle-91616

11/13/2019, 9:25 PM
i assumed that it happens when you start making really large pex files and try to execute them immediately as part of an interactive application
a previously unknown use case to me but seems like it could exacerbate any issues
h

hundreds-father-404

11/13/2019, 9:27 PM
I’m not sure if they’re added at runtime..hm. Definitely not at build time so that Pexes are reproducible for V2
a

aloof-angle-91616

11/13/2019, 9:32 PM
we should take care not to affect use cases that don’t need that reproducibility though
r

rough-minister-58256

11/13/2019, 10:30 PM
probably something that needs to be benchmarked and profiled for optimization