fluidB
/
fluidb-old
1
0
Fork 0
Code Pull Requests Activity
You cannot select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
master
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from '86d02b675e'
${ noResults }
fluidb-old/aws
History
Mauri de Souza Meneguzzo 69933cbe35 aws: reuse session and S3 manager 
The AWS session and s3 manager are concurrent safe, it should be reused
whenever possible:

    Sessions are safe to use concurrently as long as the Session is not
    being modified. Sessions should be cached when possible, because
    creating a new Session will load all configuration values from the
    environment, and config files each time the Session is created.

See https://pkg.go.dev/github.com/aws/aws-sdk-go/aws/session

Currently, an aws session and s3 client/manager are created every time a
call to Upload, CurrentID or Download is made. I changed it so it creates
one session and S3 manager during app startup and reuse it afterwards.
 		8 months ago
..
s3.go aws: reuse session and S3 manager 8 months ago
s3_test.go aws: reuse session and S3 manager 8 months ago