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-02 : 12:59:22
|
| Hi all, Need some help with configuring the Disk Sub system using Raid 101. What shud be the disk configuration to have 4000 inserts per second on a RAID 1+0 ?2. What is the best way to maintain a Hot Stand by Server for a very high OLTP system ( say for a day Trading Database ).ThxVenu |
|
|
MichaelP
Jedi Yak
2489 Posts |
Posted - 2006-03-02 : 17:35:50
|
| 4000 inserts per second? Is that for short periods of time, or 4000 rows per second for an 8 hr work day? How many bytes (on average) is a row? For something like this, I think that a "Hot Standby" is not what you want here. I think you want to setup a "Failover Cluster" so that if one server has an issue, it automatically fails over to the other server with no human intervention. Your "downtime" should be somewhere around 30-90 seconds in that case. If you design your appllication to handle such an event, your users probably will never know the failover happened.With all that being said, what sort of budget do you have for this project? You are easily looking at $100k, and probably closer to $200k for that level of performance and reliability. 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> |
 |
|
|
avmreddy17
Posting Yak Master
180 Posts |
Posted - 2006-03-03 : 17:20:07
|
| Just curios what kind of disk configuration we shud have to handle that kind of load 4000 inserts per secondWe want to have a back up machine if the cluster fails .. we are already running with a Active/passive Cluster. |
|
|
|
MichaelP
Jedi Yak
2489 Posts |
Posted - 2006-03-03 : 17:50:08
|
| "4000 inserts per second" doesn't give me enough information to help you solve this problemWe need to know 1. The average size of each insert in bytes (either that or just take the maximum size of a row and use that number as a "worst case")2. The 4000 inserts Is that a "burst" number where you need to do 4000 inserts a second for a really short period of time, or is this a "sustained" number where you need to do 4000 inserts per second for 8-10 hours a day.3. What else is going on in this database or on this disk subsystem? Could there be other factors that would lower your throughput below 4k per second?4. What sort of growth do you expect? Do you need to be at 8k inserts per second in a year? etc.Based on information from the other post, your worst case is about 16MB/sec write. On average you can get about 3-5MB/sec write per physical drive, so that puts you somewhere around an 8-disk RAID 1/0 array to be able to meet your minimum spec. I'd shoot for a 10-disk array just to be certain.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> |
|
|
|
|
|
|
|
|
Configuring DISK Sub System