Hi @Devendra Yadav ,
...Could you guys suggest what should be optimal metrics for this on SQL server or this is normal?
Quote from this doc. : monitoring-disk-usage
...
Less than 10 ms - very good
Between 10 - 20 ms - okay
Between 20 - 50 ms - slow, needs attention
Greater than 50 ms – Serious I/O bottleneck
...
So for your case , 500-1000ms is serious bad.
Follow steps as this doc. to troubleshoot the issue : how to troubleshoot SQL Server I/O-related issues
Workaround:
Quote from this doc.: slow-storage-reads-writes
...
To Fix the Problem
There’s two ways to fix slow storage: make the storage go faster, or ask the storage do to less work.
The second option – asking storage to do less work – is usually the easiest way to start. By dropping unused indexes, we can insert/update/delete data faster, run backups faster, do DBCCs faster, and even do index rebuild jobs faster. By using the right indexes, we can avoid storage-intensive table scans and do less data juggling in TempDB.
...
More information: how-to-examine-io-subsystem-latencies-from-within-sql-server ,monitoring-read-write-latency, monitor-sql-server-io
BR,
Mia
If the answer is helpful, please click "Accept Answer" and upvote it.