Support #330
IB server refresh - New Production Server
| Status: | Closed - End of life cycle | Start date: | August 06, 2010 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | August 06, 2010 | |
| Assignee: | - | % Done: | 100% | |
| Category: | - | Estimated time: | 1.00 hour | |
| Target version: | - | Spent time: | - |
Description
Maybank Singapore is planning to do a server refresh for their production server. Based on the specification provided below, it is OK for them to remain with their current IM & FI configuration? The current configuration is 8 FI and 8 IM with 16 thread. Is the configuration optimized?
The following server is for BV server :Sun Sparc Enterprise M3000 or equivalent
- 1 X 2,52GHz 2-Core UltraSPARC 64VII
- 8GB Memory
- 2 X 146GB Hard Disk
- DVD-ROM Drive
- 1 Quad Gigabit Ethernet Card
Relative Performance M values: 36000
Sun Sparc Enterprise T5120 or equivalent
- 1 X 1.2GHz CPU (8-cores)
- 16 GB Memory
- 2 X 146GB Hard Disk (configured as RAID 1 for OS)
- 1 X Graphic Card
- DVD-ROM Drive
- 4 X Gigabit Ethernet Port
Relative Performance M values: 250500
History
#1 Updated by Anonymous about 14 years ago
- Status changed from New - Begin Life Cycle to Work Completed-End life cycle
- % Done changed from 0 to 100
- Estimated time set to 1.00
Current configuration: 8 FI & 8 IM with 16 thread => OK, based on the old server specs
Can IM & FI be increase on the new server?
Some general information that could be helpful in determining the number of IM.
You can set a 1:1 ratio of 1to1 servers (e.g. cntdb, cmsdb) to IM engines, plus add the extra servers for pub center, DCC, etc so usually you'll end up with a few more than IM engines. Normally you can configure 2-4 IM engines per CPU depending on load. If you increase the number of IM engines you will need to increase the 1To1 server accordingly. You can configure the number of threads up to 16 threads per IM engine. Any number more than this will not make any big different.
#2
Updated by Tan Lee Yong about 14 years ago
- Status changed from Work Completed-End life cycle to Closed - End of life cycle
#3 Updated by Anonymous almost 14 years ago
- Tracker changed from Task to Support