1 / 18

Classic GUI 2dmap r11 Scalability Tests

Classic GUI 2dmap r11 Scalability Tests. Objectives. The main objective is to determine the time it takes to launch classic gui 2dmap with large number of Worldview objects in MDB. Analyze the impact on status changes with large number of objects. Test 1. Delta vs. Non Delta mode.

pascale-cole
Download Presentation

Classic GUI 2dmap r11 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. Classic GUI 2dmap r11 Scalability Tests

  2. Objectives • The main objective is to determine the time it takes to launch classic gui 2dmap with large number of Worldview objects in MDB. • Analyze the impact on status changes with large number of objects

  3. Test 1 Delta vs. Non Delta mode

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

  5. catng2d MDB Setup Ingres MDB Server MDB

  6. Verify WV Objects 109,264 WV Objects in MDB

  7. Non Delta Mode

  8. Non Delta Mode Launch time approx 8 minutes

  9. Delta Mode Launch time approx 1 minutes

  10. Conclusion • Non delta mode takes approximately 8 minutes to launch 2dmap where as in delta mode it only takes about 1 minute. • Ingres Remote MDB

  11. Test 2 Status Changes

  12. Objectives • With large number of objects, identify the maximum number of status changes that can be processed • This simulates Agent Technology aws_dsm generating large number of status changes

  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, it is processing 32.5 events per second. • The test setup selected is a worse scenario as MDB is not local and the status storm was generated. • This generates lot of database updates and Ingres tuning may be required

  18. Questions?? • Mail to: • Yatin Dawada • Yatin.Dawada@ca.com • Bill Merrow • Bill.Merrow@ca.com

More Related