GilaMonster (10/9/2013)
60ms isn't bad. Not perfect, but way better than I've seen in many cases.If you're seeing IO bottleneck on TempDB, splitting the user DB into multiple files isn't going to do much.
I think that time is mainly because it's raid 5, the parity check delays a bit...
The user databases have from 22ms to 9ms...
Tempdb has 4 500MB files but it's real size is already 2.5MB witch means it has grown over the estimated start size (2GB).
Since there are only 4 cores I'll change tempdb to 2 2GB files and see what happens...
Also the main user database has 100GB and it's file growth is set to....... 1MB. 1 single sales operation makes the database grow 5 times... I'll set that to 200MB witch leaves "room" for almost 2 months of data.
Thanks,
Pedro