II12506: NPM CONSOLE JAVA GUI PERFORMANCE TEST RESULTS. * OFFICIAL TESTING PERFORMED BY NPM DEVELOPMENT *

APAR status

• Closed as canceled.

Error description

• ******************************************
  *  NPMCONSOLE JAVA GUI PERFORMANCE TEST  *
     *  OF NPM CONSOLE VIEW REPAINT PROBLEM.  *
     ******************************************
  
  This info apar was created to explain the results
  of testing the current functionalities and limits
  of the NPM Console, also known as the NPM JAVA GUI.
  The testing was performed by NPM development using
  the NPM Console version 2 release 5 at the highest
  maintenance level then available, apar OW42475.  The
  testing encompassed opening and running various
  combinations of DataViews and QuickViews for
  different monitored resource and counter types.
  
  Overall, the testing showed some sort of degradation
  in the repainting of the NPM Console's views.  The
  time span before this would occur depended on
  several factors (see results below), but even under
  best conditions, it would always start no later than
  after twelve hours of continuous running.
  
  This degrading in the quality of the view's graphics
  was typically seen as blank or white or gray areas
  in the charts.  Sometimes the background behind the
  window would show through, or one part of the
  data/quickview's graph would be overlaying another
  part.  This is typically referred to as 'the screen
  repaint problem'.
  
  The tests performed show the problem is strongly
  dependent on the PC's power (CPU clock speed and
  amount of RAM), and the host NPM's REFRESH interval,
  as well as the number of views simultaneously
  running and the number of different monitored
  resource types and counters used.
  
  
  ******************************************************
  * NPM Development recommends an NPM REFRESH interval *
  * of 5 minutes (or longer) and an 800 MHz PC with    *
  * 512MB - 1GB of RAM to run the NPM Console.         *
  *                                                    *
  * Hardware/Software used during performance testing: *
  * Test machine     : IBM Personal Computer 300PL     *
  *                    Pentium III                     *
  *                    700 MHz. - 128MB RAM            *
  * Operating system : Windows NT 4.0                  *
  ******************************************************
  
  
  Here is a list of NPM Development's Test Reports,
  showing how many resources were monitored and how
  many hours it was possible to use the NPM Console's
  data and quick views without encountering window
  repaint problems:
  
  TEST REPORT             TIME LIMIT       NOTES
  --------------------------------------------------------------
  8  RESOURCES            8.00+ hours      A slow repaint
     in 2 DATAVIEWS                        appeared after 6+
          (windows)                        hours.
  
  9  RESOURCES            3.00+ hours
     in 3 VIEWS
  
  10 RESOURCES            3.00+ hours      Slow repaint appeared
     in 3 VIEWS                            on NPM/GUI windows
                                           after around 1 hour.
  
  15 RESOURCES            2.30+ hours
     in 4 VIEWS
  
  16 RESOURCES            1.30+ hours      Slow counters update
     in 4 VIEWS                            after 1 hour.
  
  18 RESOURCES            1.30+ hours      Never fully repaint
     in 5 VIEWS                            NPM/GUI windows
  
  22 RESOURCES            1.30+ hours      No repaint happen
     in 6 WINDOWS                          to NPM/GUI windows
                                           console
  
  
  
  
  Keywords:
  NPMINFO   565504300 HNR2250 V2R5M0 NPM Netview Performance
            Monitor GRAPHICS PAINTING GHOST INCORROUT
            INCORRECT BAD OUTPUT  NPMINFOAPAR
            HNR2260 V2R6M0 R260 260 V2R6 V2R6.0
  

Local fix

Problem summary

Problem conclusion

Temporary fix

Comments

• NPMINFO INFOAPAR 565504300 R250 V2R5M0 V2R5
  

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

Applicable component levels