Terminal Server slows down - cookwhisente

I have 2 TerminalServersWindows Server 2008 R2 along my farm, 25-30 hoi polloi are actively operative on each of them. They are engaged in normal office work: creating and editing documents in Microsoft Office 2010, working with mail in Microsoft Outlook 2010, surfboarding the Internet, on the job with 1C: Enterprise 8.3 and past office trifles. They are supported away 2 sufficiently powerful servers with two Xeon on for each one side, 32 GB of Wa, a RAID SAS controller with 10k and 15k disks.

Until the number of users approached 30 on each waiter, thither were no tangible inhibitions that interfered with normal surgical procedure. When they came to this figure, the servers began to significantly lentissimo down, annoying users. Braking overt in the delays of the usual trading operations of editing, creating, moving files, navigating folders. Everything seems to work, but in some way slowly, annoying, sometimes the picture freezes for 1-2-3 seconds, so the work continues.

We carry out tests

Began to understand what was the matter. First of entirely, I thought about the disk subsystem, which simply could not cope with the loading. To verify this, opened the "Functioning" grab-in, added the "Average Disk Length Queue/sec "counter, an instance of "_Total" And began to follow. My confirmation was correct. The average value was around 2-4, which is bad. Brakes begin to follow felt at values from 1.5 and higher up.

Recommendations happening the Internet suggest that, with a value above 1, the disk subsystem does not cope with the load and something needs to be through to increase performance. In my case, improving performance means buying new, fairly expensive server SSDs, As now in that respect are expensive and imperviable SAS drives with a revolution speed of 15k.

I decided to do or s more testing. I chose the same parry, but I took 2 legitimate disks separately every bit an instance. Here I was certain a surprisal. Information technology turns out that the load was not on every disks, just simply on the logical organisation partition C: where the operating system is installed. All user information is stored on disk D:, the load on it was in the range of 0.2-0.5. I earlier assumed the opposite. I thought that the section with user data is loaded, where multi-G PST files of Outlook are stored, which are constantly loaded during the work of the mail client.

Information technology is worth talking about the raid levels that I old. Now information technology became clear that I was breaking the disks incorrectly, expecting an increased load on the partitions with user data. SystemWindows Server 2008 R2installed on aRAID-1 arrayconsisting of two disks. User data is on aForay into-5consisting of 4 disks. What I was guided past when I crashed disks in this way, directly I don't remember, simply this is clearly dishonourable. I think it was necessary to pretend peerless commonRAID-10surgeryRAID-6partition, split up it into 2 logical ones, and place the scheme separately from user data. Thus, there would constitute a more uniform lade connected totally disks.

We reduce the load on the hard disk

The main task was to reduce the lode along the system of rules magnetic disk. First of all, transferred the paging single file from the system disk to the user partition. This did not help much since there is enough RAM, the use of the pagination file was minimal. I began to look with the avail of the resourcefulness monitor, what loads the nearly disk subsystem.

Information technology rotated out that browsers, in my case Internet Explorer and Google Chrome, and specifically, their caches. Began to think about how to move the memory cache. With Chromium-plate everything off out to be simple. For him, there are ADM files for managing settings finished windows region group policies. You can download them Hera " https://support.Google.com/chrome/a/suffice/187202?hectolitre=nut ".

Directory For User Data

Future, we create a new insurance policy, minimal brain damage an ADM template, find the setting "Qualify a directory for user data ", pose the value to "D: \ $ {user_name} \ Application Data \ Chrome". After applying this background, the exploiter profile from the C drive will constitute moved to the specific path. In the same order, in the settings, we indicate the maximum size of the hive up folder: "Set disk hive up in bytes " equalise to 50 MB, set the assess in bytes to "52428800".

With Internet Internet Explorer, everything was more complex. I could not find the setting in the chemical group policy that allows you to move the Temporary Internet Files folder to another position. There was an option to use a roaming profile, only I did non want to get involved with this for the interest of so much a job. I found one setting that partially could help me in my question: "Empty-bellied Temporary Internet Files folder when the browser is closed".

Turned it on so that the temporary Cyberspace files are automatically cleared when you close the browser. Although I have designed in the US Government Printing Office impressive folders (Folder Redirection ) «the AppData (Roaming booklet)» to a antithetic drive, the system is not a part of the settings still are non transferred and cadaver connected the system repulse, including the folder Temporary Net Files.

Internet Explorer

These settings shrunken the load on the system partition. Further, information technology was decided to abandon the server antivirus Kaspersky, the need for which has disappeared. Earlier, I configuredApplocker on terminals toprevent discretionary executables from running. Users could run lonesome a rigorously limited sic of programs, so they would not be able to start astir if they wanted to. Unhealthful antivirus has reduced the load.

Observant further the load on the disk, I detected that the Zabbix monitoring system of rules agentive role log is perpetually being transcribed to the file. It turned impermissible that later installation, during debugging, I indicated the maximum level of logging, which LED to the continuous recording of all sorts of information in the log. This created a decent load on the saucer since there was a lot of recorded information per second. Turned off the logs, since the system has long been configured and debugged, there is no need for logs.

Afterwards every last my actions, the disk load has decreased to acceptable values of an average queue distance of 1-1.5. Users felt an advance in speed, so the issue of the ascent was postponed for whatever time. Sooner, it is necessary to all substitute the waiter, rather than individual drives.