Pat [MSFT]
Guest
|
 Posted:
Tue Aug 09, 2005 12:18 am Post subject:
Re: recomended nubers of files per directory. |
|
|
From a server perspective, it doesn't really matter - i.e. the number of
files in a directory does not affect to a great extent the responsiveness
(except in the case of file creation and even that is not a big deal if 8.3
name creation is disabled). The perf issue you are seeing is pretty much a
client phenomenon. From the client perspective (i.e. using Explorer or any
other GUI based file management), the delay is caused by the time it takes
to iterate the files. From a CMD window if you switch to the directory,
there is no lag b/c the client doesn't iterate the files until you do a
'dir'.
So, the time will increase linearly with file count. The optimum number
then becomes whatever user experience you are going for and the network
latency (not bandwidth) between the client and the server. Cut the file
count in half and the delay cuts in half. Double it and it doubles. From
your data below the client is iterating ~600 files per second. So for a 10
second max you should limit the file count to 6000. If you need more files
in the dir, you may consider changing how the files are managed. As a rule
for high file counts (10's of thousands) it is hard for a user to manually
wade through the files anyway and scripting/specialized clients are more
appropriate.
Pat
"Tal Bar-Or" <TalBarOr@discussions.microsoft.com> wrote in message
news:6727EE22-256D-436D-B189-E1A4726D60C2@microsoft.com...
| Quote: | Hello All,
i have a storage unit shared on the network with one directory with more
than 57000 files on same directory.
when i am browsing the \\server\share its take up to 1.5 min to list
content.
My question is what is most recomended to divide # of files per folder to
get better performance.
also microsoft article aboute this issue will be appreciated.
thanks
|
|
|
FAQ
Memberlist
Register
Profile
Log in to check your private messages
Log in