|
On Apr 11, 2019, at 8:21 AM, Joe Pluta <joepluta@xxxxxxxxxxxxxxxxx> wrote:
I agree with that sentiment, John. The last time I had a situation where we had a large number of files in a directory, we started seeing various performance issues. Lists took much longer than simple linear math would have suggested, some utilities couldn't handle the number of files, various commands in QShell had problems, and so on.
Generally speaking, I prefer to limit the number of files to the low thousands. After that, I try to come up with a subdirectory management structure.
On 4/11/2019 10:12 AM, John Yeung wrote:
On Thu, Apr 11, 2019 at 10:08 AM Doug Englander
<denglander@xxxxxxxxxxxxxxxxxxxxxxxx> wrote:
We have one IFS folder with over 261,000 PDFs in it. I am wondering what the limit is so I can be proactive and avoid a problem.In my opinion, quarter of a million objects in one directory is way,
way, way, way, way too many already. Obviously, it's best if you're
proactive right from the beginning. I have a rule of thumb: If I
stumble upon a directory and I have to wonder if it has too many files
in it, then it has too many files in it.
What counts as "too many" for my sensibilities is so far below any
hard limits that I keep forgetting that there can even BE hard limits,
other than total disk space.
John Y.
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxx for any subscription related questions.
Help support midrange.com by shopping at amazon.com with our affiliate link: https://amazon.midrange.com
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.