On 09/16/2014 09:12 AM, Ski Kacoroski wrote:
> Hi,
>
> We installed a new student records system over over the summer that
> runs on MS SQL server. Everything seems to be ok, but for one thing
> that I am not sure is an issue waiting to bit me or something I can
> ignore. On the SAN, the volume for the transaction logs has 125ms
> read response times (write response times are around 2ms). This is
> the only volume on the SAN with such large response times. Has anyone
> seen this before and if so, is it something I need to be concerned about.
Since write times are fast, then it's not likely a SAN congestion
issue. Is the transaction log RAID5? Are there rebuilds in progress?
125ms is really really slow. It's about 10x slower than the real
underlying disk - including seek times. Unless you have a rebuild
underway, it sounds broken to me.
If you can afford it (and you probably can), I'd recommend RAID10 for
transaction logs - or even RAID1 SSD (even though it's pricey,
transaction logs aren't usually huge).
-- Alan Robertson
[email protected]
_______________________________________________
Discuss mailing list
[email protected]
https://lists.lopsa.org/cgi-bin/mailman/listinfo/discuss
This list provided by the League of Professional System Administrators
http://lopsa.org/
