Windows 2000 Distributed File System Performance
Hey Everyone I'm looking for some opinions about the performance of Windows 2000 Distributed File System (DFS) when dealing with a very large number of small files. Please reply with personal experiences using DFS and any impact on performance of the servers.
Hey Everyone
I'm looking for some opinions about the performance of Windows 2000 Distributed File System (DFS) when dealing with a very large number of small files. Please reply with personal experiences using DFS and any impact on performance of the servers.
I plan to implement a DFS share to replicate the wwwroot on 3 web application servers. The wwwroot contains about 230,000 small files in 24,000 folders. Total size is about 3 GB but the files rarely change. All three servers are large machines running Windows 2000 Server (SP3) with hardware SCSI RAID and are connected via 100mbit lan. I fully understand how to implement this but am looking more for input on the performance hit I can expect when replicating such a large number of files.
Thanks for any help,
Evan
I'm looking for some opinions about the performance of Windows 2000 Distributed File System (DFS) when dealing with a very large number of small files. Please reply with personal experiences using DFS and any impact on performance of the servers.
I plan to implement a DFS share to replicate the wwwroot on 3 web application servers. The wwwroot contains about 230,000 small files in 24,000 folders. Total size is about 3 GB but the files rarely change. All three servers are large machines running Windows 2000 Server (SP3) with hardware SCSI RAID and are connected via 100mbit lan. I fully understand how to implement this but am looking more for input on the performance hit I can expect when replicating such a large number of files.
Thanks for any help,
Evan
Participate on our website and join the conversation
This topic is archived. New comments cannot be posted and votes cannot be cast.
Responses to this topic
funny that you bring that up because i use DFS on my .NET servers to do the exact same thing. Ihave my wwwroot for all the website that i have built on 2 computers using DFS. Updates to file happen almost instantaneously. What DFS does is like binds the 2 or more folders together into what they call a domain root. Then you can work on that share and it will auto replicate to the others. It is pretty cool to cause the share is like virtual like \\nameofdomain\nameofdomainroot
so it is really easy to get to. then you can just point all your IIS home dirs to that share also. It allways worked great for me in .NET i am not sure how it works in 2k but i imagine it is just the same
so it is really easy to get to. then you can just point all your IIS home dirs to that share also. It allways worked great for me in .NET i am not sure how it works in 2k but i imagine it is just the same
Thanks for your reply Four and Twenty. How many files do you have in your wwwroot? Did you notice any performance hit?
pmistry, here's a great link to learn more about DFS( http://www.labmice.net/Windows2000/FileMgmt/DFS.htm). Its a pretty sweet way of giving yourself fault tolerant file shares.
pmistry, here's a great link to learn more about DFS( http://www.labmice.net/Windows2000/FileMgmt/DFS.htm). Its a pretty sweet way of giving yourself fault tolerant file shares.
no performance hit that i can see
DFS works great.
holy crap you have a lot of files
I just write my web apps by my self for small local biz
what the hell kinda apps are you guys writing?
I just write my web apps by my self for small local biz
what the hell kinda apps are you guys writing?
Hehe yes we have WAY too many files. The problem is our web software was written by someone who thought it best that every client had their own folder (with a copy of master version files) and every client project had its own sub-folder (also with a copy of master version files). Multiply this by 3 major products (and multiple versions of each) and we have a lot of the same files in different folders with a few customizations here and there. These files will eventually be archived but not in the near future. Luckily our new versions of software will be less file intense
