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
I've swapped over to using S3 for file storage and, as many know, it's extremely slow with filebrowser. I've taken the time to track the problem down!
The issue is the get_directory() function in filebrowser_safe/functions.py. Hover, I've been extremely lazy and not tracked the issue past this. In my fork I've just deleted everything except for dirname = DIRECTORY and return dirname because I don't use the site system anyways. master...overshard:master
This makes my filebrowser just as fast as if I were storing files natively, a directory of 10k files loads up in less than a second for me, before it would freeze and timeout with more than 5 files in the directory. I believe the problem is too many calls are being made to S3 due to this one function.
Obviously the solution is not what I have here but I wanted to bring this to everyone's attention because I know it's a problem point for many wanting to use S3 and someone can craft a solution based on my discovery. And if other people aren't using the site system you can use this till it actually gets fixed.
The text was updated successfully, but these errors were encountered:
I've swapped over to using S3 for file storage and, as many know, it's extremely slow with filebrowser. I've taken the time to track the problem down!
The issue is the
get_directory()
function infilebrowser_safe/functions.py
. Hover, I've been extremely lazy and not tracked the issue past this. In my fork I've just deleted everything except fordirname = DIRECTORY
andreturn dirname
because I don't use the site system anyways. master...overshard:masterThis makes my filebrowser just as fast as if I were storing files natively, a directory of 10k files loads up in less than a second for me, before it would freeze and timeout with more than 5 files in the directory. I believe the problem is too many calls are being made to S3 due to this one function.
Obviously the solution is not what I have here but I wanted to bring this to everyone's attention because I know it's a problem point for many wanting to use S3 and someone can craft a solution based on my discovery. And if other people aren't using the site system you can use this till it actually gets fixed.
The text was updated successfully, but these errors were encountered: