I saw that there is a requirement is for a public files directory for saving and serving CSS. When I use the awssdk and amazons3 modules, making the amazon storage the default download method for my files, immediately there is a multi-second delay added to every page-load. The delay is for drupal to first start sending the page to the browser. I'm not sure if this is something that can be fixed in the module, or if it is just an inherent incompatibility, but I thought I'd file it here.

Thanks,
-Joseph

Comments

jtbayly’s picture

jtbayly commented

One workaround: If it isn't strictly necessary for Amazon S3 to be the *default* file system, then simply use the default local file storage and use the Amazon S3 storage with whatever individual fields you want stored up there. The performance problem will go away as soon as you switch the default storage to the local filesystem.

sreynen’s picture

sreynen commented
Status: Active » Closed (duplicate)

Since the whole point of Amazon S3 is faster file loading, I'm guessing the problem here is writing, not reading. More specifically, I think this is a duplicate of #1165658: Only re-write font.css when CSS changes. I'll change that to a bug now that we have a documented problem it's causing and it's more than just "this could be faster."