So you're telling me that the guest OS uses a significantly different amount of memory based on what hypervisor it's running under, given an identical workload? I don't think I buy that One obvious problem I see is that Internet Explorer is obviously a very heavily used application on your terminal server, however, you're using a mix of bit and bit instances of Internet Explorer.
If you standardized all your users on either 32 or 64 bit Internet Explorer, your overall memory usage would be less. After user logon, the desktop or application if in single-application mode is displayed for the user. When the user selects a bit application to run, the mouse commands are passed to the Terminal Server, which launches the selected application into a new virtual memory space 2-GB application, 2-GB kernel.
All processes on the Terminal Server will share code in kernel and user modes wherever possible. When multiple processes want to read and write the same memory contents, the VM manager will assign copy-on-write page protection to the memory region. Copy-on-write is extremely useful and efficient for applications running on a Terminal Server. When a Winbased application such as Microsoft Word is loaded into physical memory by one process Session it is marked as copy-on-write.
When new processes Sessions also invoke Word, the image loader will just point the new processes Sessions to the existing copy because the application is already loaded in memory. The VM manager will protect this memory space from other processes.
Most of an application, however, is shareable code and will only have a single instance of code in physical memory no matter how many times it is run.
The bit applications Win32 will allow sharing of code and run more efficiently in multi-user sessions. All bit output is translated into Win32 calls, which perform the necessary actions. Because Win16 apps are executing within their own VDM, code cannot be shared between applications in multiple sessions.
Translation between Win16 and Win32 calls also consumes system resources. Running Win16 applications in a Terminal Server environment can potentially consume twice the resources than a comparable Winbased application will. Sign up to join this community. The best answers are voted up and rise to the top.
Stack Overflow for Teams — Collaborate and share knowledge with a private group. Create a free Team What is Teams? Therefore, whilst we are confident that this issue can be resolved, there is a small chance that there still remains an issue.
NOTE: The issue persists on Windows 7 for which we have not plans to address this as we believe the issues lies with Microsoft. Page Loading Type: Bug. Status: Closed View Workflow. Priority: High. Resolution: Fixed. Labels: lbp lbp-bugfix ml-candidate. Sorry to hear that. Name Name is required. Email Email address is required. Close Submit.
Featured Products. Need more help? Product issues. Open or view cases Chat live. Other support options. Share this page.
0コメント