There is an async cache store wrapper, or at least there was one for
JBoss Cache, which would in fact queue and batch up all the
modifications at once. I'm not sure how this would necessarily help S3
perform better as I believe each put requires a separate HTTP request
and response. Check out the config guide.
The old S3 cache loader I worked on used the Apache HTTP Client and I
believe had some sort of HTTP connection pooling configured, though I
don't know how well it worked. As a point of comparison, you could
resurrect and port the old JBoss Cache S3 cache loader to Infinispan.
You can find this code in SVN for JBoss Cache.
On Wed, Dec 2, 2009 at 10:35 AM, Adrian Cole <ferncam1(a)gmail.com> wrote:
Hi, Phillipe.
Firstly, thanks for taking effort on this. If you have some time, I
would love for you to integrate the trunk version of jclouds as we
have significantly better logging. I'd also love to see your patch on
current effort. Seems you know what you are doing :)