Number of files in a folder...

Hi,

Is there an upper limit (or a recommendation) on the number of files I can put in a folder in a TemSite workarea? Of course, without resulting in any performance issues... TeamSite version is 6.5SP2...

Thanks,
Burcin

Find more posts tagged with

Comments

Pawan

Hi,

There is a performance issue when the number of files exceeds in a particular folder, especially if you have indexed that branch for your search.

I don't remember the exact number, its somewhere around 5000 files in one folder.

suj

In older versions of TS ie, before TS 6.x, the recommended limit was 1000 files per folder. Per, Interwoven support, post TS 6.x, there is no such limit. But it is always recommended to have lesser number of files in a directory to optimize the search/opendeploy performance. We used to have around 200,000 images in a directory and had major issues with opendeploy directory comparison performance.

embeddedCrosstab.zip

13adam13

There is, according to IW, an OS limit to number of files in a folder. Of course, only true on Windoze as far as I know. IW has indicated to me that this limit is lifted on 2003, which I have anecdotal evidence to support. On 2000, exceeding the limit would occasionally cause the IFS mount to disappear (only recoverable by a system reboot).

The limit was either 5K or 10K, don't recall which.

Adam Stoller

Hi,

Is there an upper limit (or a recommendation) on the number of files I can put in a folder in a TemSite workarea? Of course, without resulting in any performance issues... TeamSite version is 6.5SP2...

Thanks,
Burcin

Limitations have already been responded to.
Recommendation - try to keep it 500 or fewer. Why? Because if you ever have to navigate through a directory or you have "All" selected for listings in the GUI - having more than 500 files will make it more difficult / slower to do so.

As of either TS552 or 6.0 - the backing store will actually break directories up into (if I recall correctly) about 255 files per directory - which helps to eliminate the actual files-per-directory limitations and also helps to alleviate some of the performance issues - but still - if you run operations that have to stat the files and such - more directories and fewer files per directory is generally better.

Also, consider that in many of these cases you will be pushing these files to a non-TS server (e.g.: Web or App server) - and if you push 5000 files into a directory there, that's really 5000 files in a directory and not a view of 5000 files in a directory which are actually split up amongst a bunch of directories in the TS backing store.

Just because you can put all those files into a single directory doesn't mean you should.