|
Aaron, I think this was brought up over at Ignite400.org (you may want to dig in the mailing list archives there). Large numbers of files do cause problems when browsing files but as far as serving them goes, it's not much of a problem until you hit the limit (I don't recall what that it). The person who was having problems had to deal with really large numbers of files (I want to say it was over 100,000 -- they were running a site for the auto salvage industry and had several pictures each of salvaged cars). We have a directory that got over 50,000 files in it over time (I believe that WRKLNK didn't have any problems outside of being slow). It was a real pain to clean up because the Qshell utilities couldn't handle that many files so I couldn't write a script to do the cleanup. I think I had to deal with them through either FTP or using one of the programs from IFSTOOL to do it. Matt -----Original Message----- From: rpg400-l-bounces@xxxxxxxxxxxx [mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of albartell Sent: Thursday, March 02, 2006 2:52 PM To: 'RPG programming on the AS400 / iSeries' Subject: Many IFS files in directory I was just thinking today about a project that I am working on that is cataloging 22,000 PDF invoices (per day) on a Windows machine and the approach we have taken to ensure top performance is to put no more than 1000 files in each directory by dynamically creating new directories multiple levels deep instead of putting all files in one directory. I thought this was just a Windows problem but then a co-worker of mine said Linux had the same problem (or similar at least), and that got me thinking about all of the files I write out to the IFS with RPG. Does anybody know if the IFS base file system suffers from the same dilemma? Thanks, Aaron Bartell
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.