![]() I also looked in the "Resource Monitor" on the disk use but the sql server only use around 8-300 B/sec and that not very much. When I looked in the "Task Manager" at the SQL server I saw that the SQL server only used around 250MB of RAM, I think that if the SQL server use more RAM it will not write to the disk so often? Or am I thinking wrong? The memory setting on the SQL Instance is ![]() ![]() I have moved the disk from our NAS (iSCSI) to a local disk on the VMWare host because i tought it might been the NAS that was "overloaded" but the spikes are still there. I got a lot of spikes on the "Datastore Read Latency" on a VMWare ESXi host from two VM's on thas has Veeam Backup and Veeam One installed, but thoose spikes are not so hight around 20ms but then I got higher spikes from a server that hosts a SQL Server, thoose spikes are around 20-80ms and the people that's working on a system to that SQL Server are complining about lags.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |