Improve windows 2008 file server performance

Originally it all appeared to work okay, then at some point later things got slower and slower. I haven't done any more to see if the indexing database was corrupt, which might explain things. Killing the service those threads started dropping like flies, and the primary task of moving data was able to continue - finally unimpeded. I didn't try turning off the search, but reading your note made me think about other things to turn off.

I'm going to go back and see what settings I have in the firewall that are causing my problems, but wanted to post this My issue was copying files from an Windows 7 computer to a Windows Home Server either took many hours, or not at all.

And when I'd try to stop a hung copy it would freeze up the explorer on he windows 7 machine causing me to have to reboot completely. The following NIC performance tuning settings should improve file transfers between Windows 7 and Windows systems:. I know that this thread is very old, but since a big search engine showed this place on its first page, I will add my experience here for posterity:. No anti-virus at either end. Same hardware, including target disk SATA2 both cases.

Not only that, but the XP3 was loaded with quite a bit of junk, while the R2 was pristine, and except of IIS no other meaningful role was installed. I disabled on the R2 all disk indexes - no change. Looked at suspicious services - none. No Win Search service either. Perfectly resolved the issue.. Its the network adaptor parameters that creates this issue.. Office Office Exchange Server.

Not an IT pro? Windows Client. Sign in. United States English. Ask a question. Quick access. Search related threads. Remove From My Forums. This will ensure that the CPUs are always clocked at percent and that no processor cores are parked.

Keeping the CPU at full power improves disk input-output when there is a constant and heavy load. Configure the power plan using Group Policy or using local machine policy for servers not joined to a domain, as power settings have a habit of resetting after Windows patches and hotfixes are applied.

To set the power plan using local machine policy, log on to your server as a local administrator:. DOS 8. Directory enumeration can be up to 10 times faster when files are stripped of their 8. The defaults are and , respectively. These parameters allow the server to throttle client operation concurrency dynamically within the specified boundaries. Some clients might achieve increased throughput with higher concurrency limits, for example, copying files over high-bandwidth, high-latency links.

Prior to Windows 10 and Windows Server , the number of credits granted to the client varied dynamically between Smb2CreditsMin and Smb2CreditsMax based on an algorithm that attempted to determine the optimal number of credits to grant based on network latency and credit usage.

In Windows 10 and Windows Server , the SMB server was changed to unconditionally grant credits upon request up to the configured maximum number of credits. As part of this change, the credit throttling mechanism, which reduces the size of each connection's credit window when the server is under memory pressure, was removed. Since the server no longer shrinks credit windows the Smb2CreditsMin setting is no longer necessary and is now ignored.

The default is 0, which means that no additional critical kernel worker threads are added. This value affects the number of threads that the file system cache uses for read-ahead and write-behind requests. The default is Increasing this value raises the number of threads that the file server can use to service concurrent requests. When a large number of active connections need to be serviced, and hardware resources, such as storage bandwidth, are sufficient, increasing the value can improve server scalability, performance, and response times.

This parameter limits the number of concurrent asynchronous SMB commands that are allowed on a single connection. Some cases such as when there is a front-end server with a back-end IIS server require a large amount of concurrency for file change notification requests, in particular.

The value of this entry can be increased to support these cases. Asked 12 years ago. Active 9 years, 7 months ago. Viewed 6k times. Improve this question. Kirk Marple Kirk Marple.

What's the client OS and is it a newer machine? What about network structure, NICs, have you run a performance test on the network? Add a comment. Active Oldest Votes. Improve this answer. Community Bot 1.