D Synchronization Performance Estimates
This section provides estimates of the transaction rates for the LNP database synchronization operations. Using these estimates can help decide which type of operation to use in choosing a database maintenance procedure.
Introduction
This appendix provides estimates of the transaction rates for the various LNP database synchronization operations. Using these estimates can help you decide which type of operation to use.
Recommended Network Bandwidth
To use any LNP database synchronization operation other than manual bulk load, it is recommended that the network connection between the LSMS and each network element have a minimum bandwidth that is equal to or greater than 50% of a T1 line (a minimum bandwidth of at least 96,000 bytes per second).
The estimates shown in this appendix assume that the LNP database synchronization operation uses bandwidth of 96,000 bytes per second.
Performance of LSMS to NE Operations
Table D-1 shows the performance estimates of various LNP database synchronization operations. These estimates are based on a single LNP database synchronization operation running on an LSMS system with minimal system activity.
Table D-1 LNP Database Synchronization Performance Estimates
| LNP Database Synchronization Operation | Connection (Note) | Data Objects Per Hour | Worst Case Performance Based On: |
|---|---|---|---|
|
Audit |
Dedicated |
24 million |
Amount of time it takes to look up data in the LNP databases and calculate checksums (LSMS - 600 objects per second, NE - 3400 objects per second) and on the number of discrepancies the LSMS finds (the LSMS can record up to 1 million discrepancies per hour). |
| Support ELAP Reload via Database Image (SERVDI) | Dedicated | 150 million | Amount of time it takes to create an LNP database image file in the LSMS (2.5 million objects per second). Time to transfer to NE is listed in Table D-3. |
|
Bulk load |
Dedicated |
8 million |
Amount of time it takes to look up data in the LSMS and create an update command (600 objects per second) transmit it (assuming 50% of T1, 750 Kbps) and insert data into NE database (333 objects per second). |
|
Reconcile |
Normal |
180,000 |
Amount of time it takes to look up data in the LSMS and create an update command (600 objects per second) transmit it (25 objects per second) and insert data into NE database (333 objects per second). |
|
Note: This is the rate for the normal update channel, which includes both normal updates and reconciles. The rate for reconciles depends on how much normal traffic exists. |
|||
Performance of NE to NE Operations
Table D-2 shows estimates of the time required to copy an RTDB across the customer network, depending on the speed of the customer network.
Table D-2 Estimating Time to Copy RTDB Across Customer Network
| Speed of Customer Network | Estimated Time to Copy One Million Numbers |
|---|---|
|
100 Megabits/second |
11.5 seconds* |
|
10 Megabits/second |
40 seconds* |
|
1.44 Megabits/second |
3.7 minutes |
|
128 Kilobits/second |
41.67 minutes |
|
56 Kilobits/second |
95.25 minutes |
|
*At this network speed, system performance is limited by ELAP disk |
|
Starting with ELAP 9.0, the database size for transfer is no longer dependent on the number of database entries. Table D-3 shows the estimated transfer times for the database as a whole.
Table D-3 Estimating Time to Transfer the Entire Database
| Speed of Customer Network | Estimated Time to Copy Database |
|---|---|
|
100 Megabits/second |
2 minutes |
|
10 Megabits/second |
15 minutes |
|
1.44 Megabits/second |
95 minutes |
|
128 Kilobits/second |
17 hours |
|
56 Kilobits/second |
40 hours |