We watched for any noticeable search result slowdown for the primary user when the secondary user’s OST files were being indexed in the background. We looked for differences in how Outlook search performs in the primary user session when using the two technologies. FSLogix secondary users started off indexed because their index roams with them (no need to rebuild if they end up on a new RD Session Host server). UPD secondary users were not indexed – this simulated the users having to re-index if they move to a different RD Session Host server. In each comparison, the number of secondary users “working” in the background was the same (0, 5, 10 and 20 users). We compared runs that used User Profile Disks to like runs that used FSLogix container technology.
![speed up outlook 2016 indexing speed up outlook 2016 indexing](https://www.stephenwagner.com/wp-content/uploads/2019/05/WaitingForSearch.png)
For each test run we gathered and analyzed the screen videos from the primary client and the Performance Monitor footage. In June 2017, we conducted 20 Outlook Search test runs. REX Analysis and Our Outlook Search Benchmarking Conclusions
#SPEED UP OUTLOOK 2016 INDEXING PC#
The Tracking Environment included a Lab Controller PC connected to the primary client (so it can capture video data from a client PC’s RDS sessions and store those videos for later analysis), and an RD Session Host server to kick off secondary user sessions to the on-prem/azure RDS environments.įigure 1 – The On-Premise RDS deployment, the Azure RDS deployment, the Tracking Component and the Client Component. Our benchmarking setup had four parts: The On-Premise RDS deployment, the Azure RDS deployment, the Tracking Component and the Client Component (see Figure 1). Build REX Analyzer 4-Up Video Panels that show the primary user experience along with certain performance monitor counters in real time.Collect metrics, performance counters and videos.Click here for more details about our compiled executables and how they work Create and compile the test sequences that will run the workloads – these are the executables that simulate user’s working in Outlook.Build both the on premises and the Azure environments (includes identical RDS deployments in Azure and on premises locations).These are the steps we performed to set up the environments, conduct the test runs and gather the results: We conducted our tests in an on-premises environment, and a duplicate Azure environment to see if there were any notable differences in a cloud based environment. In other runs, we introduced a number of secondary users who also “worked” in Outlook. In some runs only the primary user taxed the system. We recorded the on-screen user experience of a primary user, and also collected performance counter data during each test run.
![speed up outlook 2016 indexing speed up outlook 2016 indexing](https://emailmate-bc85.kxcdn.com/blog/wp-content/uploads/2019/07/Outlook-Repair-Tool.jpg)
#SPEED UP OUTLOOK 2016 INDEXING SERIES#
Users opened Outlook and conducted a series of searches that queried the local windows search service (queries against All Mailboxes, All Outlook Items or Subfolders) and queried the Office 365 server search service (queries against current folder and mailbox). We did this by collecting performance metrics as well as video footage of a series of test runs where users in remote sessions “worked” in Outlook 2016.
![speed up outlook 2016 indexing speed up outlook 2016 indexing](https://sol1.com.au/wp-content/uploads/2016/10/Outlook-Rebuild-Search-Index-3a.png)
Our primary focus was to measure how performance degrades when multiple users are simultaneously working with Outlook (“noisy neighbor effect”). We wanted to illustrate the user experience of remote desktop users working in an RDS environment configured to use FSLogix Office 365 Containers relative to the typical user experience when using native RDS UPD technology. RDS Gurus decided to run performance tests on Outlook in non-persistent environments using FSLogix’s Office 365 Containers solution. An Independent Remote End-User Experience Performance Benchmark