PM10356: Eclipse integration shows extremely bad performance

APAR status

• Closed as program error.

Error description

• Summary:
  Eclipse integration shows extremely bad performance
  
  
  Description:
  
  The results are as follows (note that the video program took
  about 30%
  CPU power):
  
  Code on local disk, standard configuration:       CG =  6
  sec, RT =
  48 sec
  
  Code in Clearcase, standard configuration:       CG =  6
  sec, RT =
  49 sec
  
  Code in Clearcase and Eclipse workflow integration:   CG = 36
  sec, RT =
  incredible
  
  Interestingly, this time there's merely no difference in RT time
  with
  and without ClearCase. I guess that the Clearcase cache is the
  reason
  why we sometimes see much longer RT times with Clearcase.
  
  With Eclipse configuration there's the problem of saving the
  .cg_info
  which takes extremely long, and there seems to be some
  questionable
  traffic between Rhapsody and Eclipse. With small models,
  however, the
  Eclipse workflow integration shows acceptable performance. This
  means
  that we cannot use the Eclipse workflow integration.
  
  
  
  A test fix was then provided to the customer:
  http://rcs-testfix.lexma.ibm.com/cgi-bin/fix_portal.pl?do_view=I
  RR-D5xcTfyXKC4z
  
  He has also upgraded to Rhapsody 7.5.1.1 and has reported a
  slight improvement in performance.
  
  CG took 6 seconds. This is much faster than before, and close to
  the CG time for standard configuration which still is 5 seconds.
  It works automatically upon focus change. Great!
  
  RT took 21 seconds. This is also much faster (and more stable)
  than before, and even faster than with the old standard RT! He
  can see no more difference between RT with Eclipse and RT with
  internal editor!!!
  
  However, There still is an additional second at code
  generation.Stability has improved, but still timeouts (or
  effects that look like a timeout) occur, and there's heavy
  flickering.
  
  
  Business impact:
  Customer cant use Eclipse integration.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  Eclipse integration shows extremely bad performance
  

Problem conclusion

• This was caused by the problem that Rhapsody did code
  generation for all classes opened in Eclipse editor. This
  has been fixed.
  

Temporary fix

Comments

APAR Information

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

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

Fix information

• Fixed component name

  TLOGIC RHAPSODY

• Fixed component ID

  5724V74RP

Applicable component levels

• R751 PSN

     UP