| Title: | Executive Information Solutions & Data Warehousing Conference |
| Notice: | Welcome to the Data Warehousing conference |
| Moderator: | 26002::HAGGERTY |
| Created: | Thu Sep 01 1994 |
| Last Modified: | Thu Jun 05 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 499 |
| Total number of notes: | 2932 |
Hello, How can we validate a server sizing for a DW? I need to configure a server for DW where the information I have is the database size 100 GB initially, 200 GB in two years and 20 users. We were requested to provide a budget, so we decided to budget the 8200 2 5/400, 2GB of memory and a dual HSZ40 for 48 disks (assumption: this is a small to midrange DW). I found a good reference document (dwsymp96), which helped a lot, but I'm still wondering if I might have oversized the server (who cares!), or underestimated. Are 2 GB and 2 5/400 enough to start with? I believe I have already asked this question before, and perhaps I should have more knowledge on DW concepts before sizing a server. Do we have any questionnaire I could fill up so that someone more knowledgable could help me with the sizing? It would help to have a tool like the one we have for SAP R3 and BAAN, specially for budgeting. Thanks in advance for your help, Katya
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 481.1 | Anybody home? | MSDOA::16.179.16.37::KLOPEZ | Ay, Caramba! | Tue Apr 22 1997 18:59 | 4 |
Hey guys, Is sizing a DW a science or an art? I'm sure there must be a better way to size a DW server. Katya | |||||
| 481.2 | List of questions needed | BIGCHZ::EZZELL | Mike Ezzell | Tue Apr 22 1997 19:00 | 19 |
I realize that sizing a system for a data warewhouse that doesn't exist yet can not be done with the precision of sizing a system to run an application like SAP that can be profiled. But ... there has to be a way to determine a ball park sizing. I am working with a consulting firm that is developing an RFP for my customer. They have asked what info they need to provide to systems vendors for system sizing. If I don't give them any suggestions, they will provide whatever they come up with. Here are some suggestions to get this started: Number of users Number of queries per hour Size of database Will queries utilize indexes or will table scans be required? Please let me know if these are the type of questions that need to be answered and what other questions should be added. | |||||
| 481.3 | call me | 26002::HAGGERTY | Kevin, NSIS, Stow MA USA | Wed Apr 23 1997 03:06 | 2 |
re: .1 it's an art...
| |||||
| 481.4 | A few pointers | UTROP1::utodhcp-197-240-171.uto.dec.com::olthof_h | Spellchecked Henry Although | Wed Apr 23 1997 09:56 | 25 |
Re .2
Careful, you only look at the retrieval side of the house. I've seen
DWs where the load (including transformation and cleaning) was the
determining factor. Some information to help:
- http://sbu.mro.dec.com/esi/dwselect/htm
- STROM training materials (ran in Europe, will run - is running - in US)
with some hints for configuring an 8400 5/440. It's all round
building a system with balanced bandwith:
- I/O: 10 MB/sec per CPU (moderate) to 25 MB/sec per CPU (demanding)
- Disks: 2-5 disks per CPU (5 MB/disk)
- Controllers: 1 HSZ52 per CPU (moderate) to 20 HSZ52 with 12 CPU
(demanding)
- Presentation delivered by Doug Williams at the last DW symposium
(AlphaServer 4100 and 8000 Systems in Data Warehousing)
- Presentation by Doug Williams from November 1995 (Configuring TL
Systems for Database Applications)
And yes, whe are not as 'on autopilot' configuring these as compared
to OLTP systems. I've been saying that we need a one day course on
the subject of configuring and benchmarking systems for Data Warehouses
for over 2 years now, but without any luck.
Best regards,
Henny
| |||||