Hi!Maybe some of you can help us :-)We've a fresh installation of SharePoint 2013 and along with that a new SQL-Server 2014 SP1 (Standard).Some facts about the SQL server:- running on ESX 6.0- 4 vCPUs- 32 GB RAM- 5 virtual disks (based on a HP 3PAR SAN [SSD only]) for system C, for data, for temp and for log (every disk NTFS 64k)We've created 4 temp files each on the temp disk (initial size 8200Mb, growing by 400MB). Based on the following query:[code="sql"]SELECT files.physical_name, files.name, stats.num_of_writes, (1.0 * stats.io_stall_write_ms / stats.num_of_writes) AS avg_write_stall_ms, stats.num_of_reads, (1.0 * stats.io_stall_read_ms / stats.num_of_reads) AS avg_read_stall_msFROM sys.dm_io_virtual_file_stats(2, NULL) as statsINNER JOIN master.sys.master_files AS files ON stats.database_id = files.database_id AND stats.file_id = files.file_idWHERE files.type_desc = 'ROWS'[/code]We have avg_write_stall_ms = 850ms, and avg_read_stall_ms = 1.2ms It's just a single instance SQL server and SharePoint 2013 is the only system which uses the instance.Does anybody know reasons why TempDB has that high write latency?For SCOM we use the same configuration (another SQL Server) . SCOM doesn't have any issues with TempDB.regards,Simon
↧