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
When I get an object ("/a") from a bucket, the following three HTTP calls are performed in order:
GET /a
GET /?prefix=a
HEAD /a
This is very expensive both computationally and monetary: the second request is a LIST, costing 10x as much as the GET.
From what I can see the trace is as follows:
S3::Bucket.get calls S3::Key.get
S3::Key.get performs refresh(false), which performs the GET /?prefix request
a bit lower in the refresh() meta information is requested
When I get an object ("/a") from a bucket, the following three HTTP calls are performed in order:
This is very expensive both computationally and monetary: the second request is a LIST, costing 10x as much as the GET.
From what I can see the trace is as follows:
right_aws (3.0.4)
vagrant@precise64:/vagrant/tagcache$ ruby --version
ruby 1.9.3p0 (2011-10-30 revision 33570) [x86_64-linux]
The text was updated successfully, but these errors were encountered: