HD66579: ADMIN : OPEN HUDGE PRODUCT - CLOSING DRAWING IS TOO LONG

APAR status

• Closed as Permanent restriction.

Error description

• ADMIN : OPEN HUDGE PRODUCT - CLOSING
  DRAWING IS TOO LONG
  Scenario:
  1- Open hudge CATProduct
  2- File - New drawing
  3- Front view generation
  4- Projection view
  5- Section view
  6- Close the CATProduct
  7- Close the CATDrawing
  Result: Time is too long to close the drawing
  .
  

Local fix

Problem summary

• ADMIN : OPEN HUDGE PRODUCT - CLOSING DRAWING IS TOO LONG
  ADMIN : OPEN HUDGE PRODUCT - CLOSING
  DRAWING IS TOO LONG
  Scenario:
  1- Open hudge CATProduct
  2- File - New drawing
  3- Front view generation
  4- Projection view
  5- Section view
  6- Close the CATProduct
  7- Close the CATDrawing
  Result: Time is too long to close the drawing
  .
  

Problem conclusion

• THIS PROBLEM IS PERMANENT RESTRICTION IN
  CATIA
  ADMIN : OPEN HUDGE PRODUCT ? CLOSING
  DRAWING IS TOO LONG
  Restriction Explanation
  The close action of a document from a CATIA
  session implies a number of treatments to clean
  the memory properly so that the CATIA session is
  correct for the continuation of the session.
  For each closed document, all its contained objects
  must be removed properly from memory. These
  treatments must be done to insure that no
  remaining object, contained by a removed
  document, stays in session. These treatments could
  cause problem further on during the rest of the
  user session and possibly corrupt the session or
  that no link towards a removed object remains
  after the removal of its containing document.
  .
  This proper cleaning of the objects of a closed
  document is not performed at File/Exit as it is not
  necessary to clean properly the memory before the
  exit of the CATIA process.
  This explains why a File/Exit is faster than a
  File/Close.
  .
  The performance problem at close is not caused by
  the CATIA software but by a limitation of the
  hardware:
  - The scenario taking place before the file/close
  action leads to a memory saturation: practically no
  memory is left available before the File/Close
  action.
  - When doing the File/Close action, memory is
  needed to perform the removal of the documents
  and as no memory is available the system uses the
  memory on disc and swaps memory pages. This is
  what causes the long time for the File/Close.
  .
  This is confirmed by the following measures:
  - On AIX 64bits - 8Gb RAM: around 3 minutes to
  close elapsed - 2 minutes 20sec CPU CNEXT -
  3427Mb CNEXT process (topas result)
  - On AIX 64bits - 4Gb RAM: around 15 minutes to
  close elapsed - 2 minutes 45sec CPU CNEXT -
  3431Mb CNEXT process (topas result)
  .
  The memory is saturated before File/Close in both
  cases.
  With more RAM memory, the closing takes less
  time as less swaps are necessary since more
  memory is available on disc.
  By-Pass
  1- The solution to this problem would be to use
  more RAM memory for users that manipulate big
  assemblies
  2- IBM could make a RAM and OS tuning of the
  machines. Thank to contact IBM to have more
  information about AIX machine tuning.
  .
  

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

Applicable component levels