search

andersundsehr / aus_driver_amazon_s3

Provides a TYPO3 FAL driver for the Amazon Web Service S3
GNU Lesser General Public License v3.0
20 stars 39 forks source link

weird issue, switched to new bucket on another account and it is very very slow #92

Closed dni closed 2 years ago

dni commented 2 years ago

Hi! I'm having a very bad issue since i switched the bucket to a new aws account, i transfered all the files an switched the bucket now all my backend pages are not loading anymore, and i cant even look into the filelist module.

does anyone have an idea what is going on and could cause this behaviour?

i tried running the fal update ref index task, it took couple of minutes but went through, but still the same issue.

dni commented 2 years ago

if i switch back to the old bucket, it is immediatly fast again...

i really have no clue what is going on... any pointers into the right direction would be appreciated...

is there something like permissions on s3?

DanielSiepmann commented 2 years ago

Our filelist is also nearly impossible to use. The issue seems the count implementation. We have all files in top folder and TYPO3 asks for the amount. The current implementation seems to fetch all files in order to do an count afterwards. Not sure if that can be optimized or all files are still needed.

We had the same issue while editing the TYPO3 record for the bucket. I could fix that with this commit: https://github.com/andersundsehr/aus_driver_amazon_s3/pull/91/commits/9e195942e105784675eda476a5da98beb9379c69 Maybe that helps.

dni commented 2 years ago

sounds interesting, but how does it explain, that it works in 1 bucket, but not in the newer bucket, same enviroment same project, just different credentials.

dni commented 2 years ago

creating a new and empty one or even one with like 5 files and folders, works fine... its just the newly created one where i synced the old files...

seems like i have to bust out the debugger today.

dni commented 2 years ago

ok, this one https://github.com/andersundsehr/aus_driver_amazon_s3/commit/5aad76c085c180ff6f93bd5cbdf193bfc4973376

fixes my issue

dni commented 2 years ago

On S3 this happens when using a bucket that has no special "folder objects" (which are created by aus_driver_amazon_s3).

the comment from the commit makes perfect sense now, the s3 cli which i used to transfered all files to the new bucket didnt create those special folder files, which triggered this behaviour on my newly created bucket.