LeonesIT
asked on
Windows 2003 fileserver x64
LS,
In the past I've had some issue's with Windows fileservers in a Citrix terminalserver enviremont when using folder redirections. Mostly this could be resolved by changing the values from the server service, MAxWorkItems and the MaxMpxCt. This can be done until a memory limit is reached. The server service takes its memory from the non pageable memory pool. This pool has a maximum size of 340MB in a Windows 2003 Standard x86 server.
Windows 2003 Standard x64 has a non pageable memory pool of 128GB. Is it true that a x64 fileserver could handle more file handles than a x86 server?
How many concurrent users with folder redirections to one file server can be handeled with x64 Windows 2003?
Regards.
In the past I've had some issue's with Windows fileservers in a Citrix terminalserver enviremont when using folder redirections. Mostly this could be resolved by changing the values from the server service, MAxWorkItems and the MaxMpxCt. This can be done until a memory limit is reached. The server service takes its memory from the non pageable memory pool. This pool has a maximum size of 340MB in a Windows 2003 Standard x86 server.
Windows 2003 Standard x64 has a non pageable memory pool of 128GB. Is it true that a x64 fileserver could handle more file handles than a x86 server?
How many concurrent users with folder redirections to one file server can be handeled with x64 Windows 2003?
Regards.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
I am still using x86 versions on all my servers so this is as far as I go. :)
Cheers
Cheers
ASKER
I've read the articles and in the second one there is a piece of information in the Reliability section.
It says:
When using the /3GB switch, Windows is forced into a constrained address space, limiting the amount of non-paged pool available. This can cause non-paged pool to be exhausted when there are several I/O requests outstanding.
In the same way that businesses used the /3GB switch, there are numerous examples of manual tuning required for 32-bit systems to remain stable and available as application demands drive systems to upper limits of kernel virtual address space on 32-bit systems. In contrast, 64-bit systems grow to the maximum limit for things like system cache, session pools, and session views regardless of the underlying physical configuration. This eliminates the administrative burden associated with the need to manually tune systems in order to accommodate demanding applications.
As I'm reading this I would think that my problem with the non pageable kernel memory would be resolved when using x64 Windows.
Does anyone has hands on experience with a x64 file server?