Expected Performance of MTC StreetSaver(TM) v.8

The following performance analysis was provided as a general guideline on the run time of the Needs and Scenario calculation, which depends largely on the size of database and the types of hardware used. It is not a suggestion of recommended hardware requirement. Generally, users can expect that run time to decrease with more powerful hardware. Assumption: No other resource-intensive software running simultaneously Database Size(# of Street Sections) Hardware Configuration Years of Analysis Needs - Run Times Scenario - Run Times Small (245) P3-500 MHz 256 MB RAM Single PC 5 45 sec 3 min: 40 sec Small (245) P3-1.0 GHz 512 MB RAM Network 5 45 sec 4 min: 05 sec Small (245) P3-500 MHz 256 MB RAM Single PC 20 1 min: 05 sec 19 min: 21 sec Small (245) P3-1.0 GHz 512 MB RAM Network 20 1 min: 30 sec 20 min: 00 sec Medium (1427) P3-1.0 GHz 512 MB RAM Single PC 5 5 min: 15 sec 38 min: 30 sec Medium (1427) P3-1.0 GHz 512 MB RAM Network 5 4 min: 00 sec 31 min: 30 sec Medium (1427) P3-1.0 GHz 512 MB RAM Single PC 20 5 min: 15 sec 3 hr: 03 min: 45 sec * Medium (1427) P3-1.0 GHz 512 MB RAM Network 20 6 min: 20 sec 2 hr: 19 min: 20 sec * Large (3620) P4-2.0 GHz 1024 MB RAM Single PC 5 3 min: 45 sec 19 min: 50 sec Large (3620) P4-2.0 GHz 1024 MB RAM Network 5 4 min: 05 sec 22 min: 19 sec Large (3620) P4-2.0 GHz 1024 MB RAM Single PC 20 7 min: 10 sec 1 hr: 30 min: 02 sec Large (3620) P4-2.0 GHz 1024 MB RAM Network 20 7 min: 30 sec 1 hr: 41 min: 19 sec Table A: Test Matrix * A low Virtual Memory (VM) message was encountered. Windows automatically readjusted the VM and the analysis continued. The longer run time is possibly due to the VM issue. Back