I worked with a user today that noticed unusually long search performance every time they search from their workstation over the Windows Client. The problem cropped up for an everyday user suddenly and will not go away.

When re-creating the same searches from the server using the Windows Client installed there, the searches are almost exactly 10x faster in each case. The searches on the server run around the same speed as they used to run for this user.

This confused me as I thought that a search is a server side request so everyone's workstations should have the same performance experience. How could it be that a certain workstation could be so much slower. The slowness is not in display of the data or anything that indicates a problem with the local OS just in the time the search progress window remains open before finishing and showing all the files.

There is nothing obviously wrong with their workstation like over committed memory or a maxed out CPU, in fact they were using a powerhouse station with 128GB of memory and 16 cores. When we check task manager, running a search does not hardly touch any local resources. I am pretty sure all it does is return a set of file names and metadata to display.