title: TempDB performance crawling; should we reboot?
body: <p><strong>A bit of background:</strong>  We have 17 different TempDB database files and 6 TempDB log files on the server.  These are spread out on different drives, but are hosted on 2 drive arrays.</p>
  
  <p>I’m seeing Disk IO response times exceeding the recommended limits.  Typically you want your disks to respond in 5-10ms, with nothing going over 200ms.  We’re seeing random spikes up to 800ms on the TempDB files, but only on one drive array.</p>
  
  <p><strong>Proposed solution:</strong>  Restart SQL server.  While SQL server is shut down, reboot the drive array hosting the majority of the TempDB files.  In addition, while SQL is down, redo the network connection to bypass the network switch in an attempt to eliminate any source of slowness on the hardware.</p>
  
  <p>Is this a good idea or a shot in the dark? Any ideas? 
  Thanks in advance.</p>