(wibl-python): meta-tool performance

[selimnairb]

Original report by Brian Calder (Bitbucket: brian_r_calder, ).

---

The wibl meta-tool appears to take a significant time to start under some circumstances, potentially related to the connectivity of the system on which it’s running. This can lead to wait times of order seconds when the operation itself is sub-second, leading to significant productivity issues.

This feels like some underlying code “call home for update” functionality; it would be better removed.

[selimnairb]

Original comment by Brian Calder (Bitbucket: brian_r_calder, ).

---

Further investigation seems to suggest that the delay here is in getting AWS credentials in the boto3 library. It isn’t clear why these are requested at startup (they appear to be cached for some time, which explains the variable performance at startup), but appears to be something to do with instantiating the library (e.g., on import).