Re: Using all the CPU's

New Message Reply Date view Thread view Subject view Author view

Jim Helman (jimh++at++surreal)
Mon, 15 Nov 93 22:50:59 -0800

Currently, you can have one draw process per pipe and one
cull process per pipe. Usually this is adequate. In
principle, an implementation of Performer could parallelize
culling, but we do not currently.

70% CPU utilization is good. If you want to run at a
constant frame rate, some headroom is usually required for a
typical eyepoint, or you must find and benchmark the worst
possible eyepoint in the database.

Actually, with only 4 CPUs and 2 pipes, you are generating
5 processes APP, CULL1, CULL2, DRAW1, DRAW2. Since two of
these processors must compete for a CPU, you might actually
have too few processors if all processes are CPU intensive.

Regarding 8-16 CPUs, the typical equation is

        2*NumPipes + 1 (for APP) + 1 (for Unix).

but applications with lots of intersections, dynamics,
behaviors, networking, and I/O may use many more.
Intersections can be N-way parallelized. CPU
consumption for dynamics, behaviors, etc. is
potentially unbounded.

rgds,

-jim helman

jimh++at++surreal.asd.sgi.com
415/390-1151

New Message Reply Date view Thread view Subject view Author view

This archive was generated by hypermail 2.0b2 on Mon Aug 10 1998 - 17:50:06 PDT

This message has been cleansed for anti-spam protection. Replace '++at++' in any mail addresses with the '@' symbol.