Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
avmreddy17
Posting Yak Master
180 Posts |
 Posted - 2006-03-03 : 17:17:19
|
| Just curios,I have four 72 GB Drive on a RAID 5Disk SpecsIO/Second = 130 per diskSpeed RPM = 15 KWhen I did a load test of inserting data into a tablewith four ColumnsCol1 INTCol2 VARCHAR(32)Col3 VARCHAR(4000)Col4 DATETIMEI could insert around 1044 Inserts per second where as I thought I could do max of 520 Inserts ( 130 * 4 ) becauseeach disk can only take 130 Inserts multiplied by 4 Disksgives me a theoritical limit of 520.Also How does the Query Analyser Connects to the datbase Server.. does it use ODBCThxVenu |
|
|
MichaelP
Jedi Yak
2489 Posts |
Posted - 2006-03-03 : 17:40:03
|
| Well "130 IO's" doesn't really translate to "number of bytes SQL Server will insert per second" You've also got to factor in any disk caching and controller caching that's going on as well. I'm not sure what the best way is for you to figure out if you can hit that magic "4000 inserts per second" number that you discussed in your other thread.On another note, you mention RAID 5. RAID 5 takes a performance hit when writing data to disk since the parity data has to be calculated. For "high performance writes" you need either a RAID 1 or most probably a RAID 0/1 setup. If you reformat that array as RAID 0/1 and redo this same test, you should see much better performance assuming that the disks are the bottleneck here.Michael<Yoda>Use the Search page you must. Find the answer you will. Cursors, path to the Dark Side they are. Avoid them, you must. Use Order By NewID() to get a random record you will.</Yoda> |
 |
|
|
|
|
|
Inserts per second