You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Following #91 , it would be nice to add some caching. When using an include the file is fetched from S3 every time, so running lots of commands under treehugger means lots of network traffic to S3. Since we only support versioned S3 URL's they are guaranteed to not change, so we could cache them indefinitely in a 'treehugger' app dir to improve the launch time for 'treehugger exec'.
That said, treehugger does have to talk to KMS for every encrypted variable, so it's only saving one of several network hops. However KMS is a faster and less variable than S3.
The text was updated successfully, but these errors were encountered:
Following #91 , it would be nice to add some caching. When using an
include
the file is fetched from S3 every time, so running lots of commands under treehugger means lots of network traffic to S3. Since we only support versioned S3 URL's they are guaranteed to not change, so we could cache them indefinitely in a 'treehugger' app dir to improve the launch time for 'treehugger exec'.That said, treehugger does have to talk to KMS for every encrypted variable, so it's only saving one of several network hops. However KMS is a faster and less variable than S3.
The text was updated successfully, but these errors were encountered: