ah, so the large images do present a problem.
yes i agree with you, the directory structure on the images needs to be rewritten, and the most typical situation is as you state, create something that would limit the directory size to something manageable, or create a UserID directory, but even then, there will be problem. the issue with dolphin is the way it stores the images as a whole.
yes 10k images 5mb in size, would take a moment to open, though, that is only if you open from SSH or even worse from cpanel. as for retrieval of the files on the system, its rather quick.
at one point in our past, there was a file limitation on the directory 32K i think it was, (rounded number) with a 64bit environment, it is presupposed that that number is now limitless, though opening that directory, is something to be challenged.
this is one of the good reasons for caching, but then again dolphin presents its own problems when considering cache.
Ok, ,my site is up to almost 2000 images. Not that many but enough to get me thinking about the future. I fully expect that number to grow to 10,000 or more on the next few months.
Has anyone ever tried opening a file folder with that many files in it? especially if a good many of the files exceed 1mbit or more?At the very least, things are going to start slowing way way down when someone tries to retrieve one of those photos.
That's too many in one place and at some point, it's going to become a problem. These photos should be broken down by username at the very least. The best of all possible scenarios would be to create a user folder and within that folder, That users individual albums should also have it's own folder.
When a GIG is not enough --> Terabyte Dolphin Technical Support - Server Management and Support