hey guys! thanks for your replies!
regarding the version, i'm using 2.7.0.
in some other context in the past, i had a quite similar app (lambda, tensorflow deps etc.) and from what i remember, the execution time was well below a second, although i'm not quite sure how long the very first invocation actually took where deps were actually loaded. but i'm sure i'll find this somewhere in my logs.
in general, what i haven't understood completely yet, is how pex's bootstrapping actually works - can it also exploit lambdas "context-preservation" mechanism as usual (frankly don't know the correct term, but i hope it's clear what i meant - so that consecutive invocations of the function do not require to reload libs etc. as long as it remains "hot"). cause in that way, loading wouldn't be that much of a problem.
@happy-kitchen-89482 yeah, good point, i actually considered this already, since my artifacts simply became huge. is there any way to exclude certain dependencies from being packed with pex? what i can think of is to simply remove them from the zip within the pipeline or is there any option in either pex or the pants lambda target i haven't found yet?
cheers!