home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!spool.mu.edu!dsinc!ub!psinntp!psinntp!allink!leonard
- From: leonard@allink.com (Leonard Primak)
- Newsgroups: biz.sco.opendesktop
- Subject: Re: Math coprocessor with ODT
- Message-ID: <1992Dec29.190445.1878@allink.com>
- Date: 29 Dec 92 19:04:45 GMT
- References: <1992Dec29.023225.23804@beaver.cs.washington.edu>
- Organization: NYNEX ALLINK Company
- Lines: 15
-
- In article <1992Dec29.023225.23804@beaver.cs.washington.edu> drupp@cs.washington.edu (Douglas Rupp) writes:
- >Can anyone tell me how much adding a math coprocessor will help response
- >time in ODT? I have a 386/40 with 64K cache and an Paradise 8514/A video
- >card. I do alot of heavy duty graphics development using a commercial
- >GKS binding to X-windows. I am wondering just how much floating point
- >is used in X? What response I get now is not objectionable, but maybe I'm
- >missing out.
-
- You are missing out. ODT's X server uses floating-point operations
- for many graphics operations. I checked this out with xeyes, if you don't
- have a math co-processor, the eyeball movement is jumpy and slow, but when
- I added a MathCo to my 386/33, the eyeball movement was smooth, and so was
- ICO's, and other animation stuff.
-
- leonard@allink.com
-