More aggressive caching

[GoogleCodeExporter]

In our application, we need to use the S3 data in a multi-node environment. The 
type of application we're using won't change an existing file. In this case, we 
can simply fetch once from the S3 bucket and keep using the local copy forever.

A first approach was implemented in the attached patch. This provides a 
"no_recheck" option that, when set to a non-empty value, will prevent part of 
the S3 accesses. In our testing, this reduced latency by about half.

Note that the consistency tradeoff is not for everybody.

Best regards.

-lem

Original issue reported on code.google.com by luisemu...@gmail.com on 25 Oct 2010 at 5:41

Attachments:

• no_recheck.patch

[GoogleCodeExporter]

Sorry for the delayed response, but thank you for the contribution.

Looks like an easy thing to incorporate and I agree not for everyone.

Are you still patching our current releases with this?

Original comment by dmoore4...@gmail.com on 13 Jan 2011 at 4:04

[GoogleCodeExporter]

Well, I kept at the version I sent the patch against. That version is
working just fine for us, so no need to change (and in the process,
invalidate the AMIs :-)

Regards.

-lem

Original comment by luisemu...@gmail.com on 14 Jan 2011 at 4:44

[GoogleCodeExporter]

I haven't heard any "me too's" on this issue -- please feel free to re-open the 
issue if you would like to see it (or have a need for it) in the mainstream 
code.

Original comment by dmoore4...@gmail.com on 5 Feb 2011 at 2:03

• Changed state: WontFix