1 / 17

Unicenter NSM r11 Classic 2D Map Basic Scalability Tests

Unicenter NSM r11 Classic 2D Map Basic Scalability Tests. Objectives. Main objectives: To determine the time it takes to launch classic 2D map with large number of Worldview objects in MDB. To analyze the impact on status changes with large number of objects. Test 1.

naida-oneil
Download Presentation

Unicenter NSM r11 Classic 2D Map Basic Scalability Tests

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Unicenter NSM r11Classic 2D Map Basic Scalability Tests

  2. Objectives • Main objectives: • To determine the time it takes to launch classic 2D map with large number of Worldview objects in MDB. • To analyze the impact on status changes with large number of objects

  3. Test 1 Delta vs. Non Delta mode

  4. Test Plan • 2D map contains 109,260 objects • wvsetup to Non Delta mode • Launch 2D map in non delta mode • Analyze the time it takes to launch 2dmap • wvsetup to delta mode • Launch 2dmap in delta mode • Analyze the time it takes to launch 2dmap

  5. catng2d MDB Setup Ingres MDB Server MDB

  6. Number of Objects

  7. Non Delta Mode

  8. Non Delta Mode Launch time approx 8 minutes

  9. Delta Mode Launch time approx 1 minute

  10. Conclusion • Non delta mode takes approximately 8 minutes to launch 2D map whereas in delta mode it only takes about 1 minute. • Ingres Remote MDB

  11. Test 2 Status Changes

  12. Objective • Identify maximum number of status changes that can be processed when there is a large number of WorldView objects in the MDB

  13. Test Plan • Launch wvscheck to collect wv changes statistics • Generate 20,000 status changes • Analyze the csv file generated by wvscheck

  14. Status Changes Test Setup Ingres MDB Server MDB wvsCheck

  15. Status Changes 520 seconds to force 20,000 status changes. The back end processing will take little bit longer to generate wv notifications for these 20000 changes

  16. Status Computations

  17. Status Computations • On average, 32.5 events processed per second. • Test setup selected represents a worse case scenario as MDB is not local and a status storm was generated. • This scenario generates alot of database updates and Ingres tuning may be required

More Related