home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!stanford.edu!sun-barr!sh.wide!wnoc-tyo-news!scslwide!wsgw!wsservra!onoe
- From: john@pluto.Jpl.Nasa.Gov (John R Veregge)
- Newsgroups: fj.mail-lists.x-window
- Subject: Xt and CPU usage
- Message-ID: <1992Dec29.083035.15249@sm.sony.co.jp>
- Date: 29 Dec 92 08:30:35 GMT
- Sender: onoe@sm.sony.co.jp (Atsushi Onoe)
- Distribution: fj
- Organization: Jet Propulsion Laboratory, Pasadena CA
- Lines: 27
- Approved: michael@sm.sony.co.jp
-
- Date: Tue, 29 Dec 1992 04:41:04 GMT
- Message-Id: <1992Dec29.044104.19377@llyene.jpl.nasa.gov>
- Newsgroups: comp.windows.x
- Sender: xpert-request@expo.lcs.mit.edu
-
- We have developed several large Motif applications that are complete CPU
- hogs and I don't know why.
-
- Each application has 300 to 500 XtCreateWidget() and 8 XtAppCreateShell()
- calls. These calls are all made before XtAppMainLoop() is called. Widgets
- are not destroyed until the application exits.
-
- Each application is driven by both the GUI and serialized data using
- XtInputCallbackProc's.
-
- We run 2 to 4 application on a workstation.
-
- 2 applications will put CPU usage of a Sparc 2 at 97%, even when
- completely idle with no serialized data input and no X events (GUI input).
-
- Can anyone tell me (1) Why? and (2) How can I fix (optimize) this?
- ______________________________
-
- John R Veregge
- Jet Propulsion Laboratory
- Calif Institute of Technology
- john@pluto.triton.jpl.nasa.gov
-