Liem Lu (LLU++at++FALCON.AL.WPAFB.AF.MIL)
Mon, 16 Jun 1997 17:20:03 -0400
What kind of performance hit do you get when you
do database paging compared to when you are not?
On our machine (Onyx RE, 8 150MHZ R4400 CPUs, 128
MB memory, 4MB tex mem, 3 pipes), the update rate
went from 30Hz to 15Hz every time I page in a FLT
file of approximately 500 polygons. The App
process was locked on CPU #1, the three Cull
processes and three Draw processes were locked on
CPU #2,3,4,5,6, and 7 respectively. I forced the
dbase process to run on CPU #0. That didn't help
much.
Is that the kind of performance I should expect
when database paging?
Also, I've noticed that even though the CPUs were
locked for my Performer processes as above, the
update rate would go down when someone run an unix
app such as the emacs editor or make. This
happens even when I wasn't doing database paging.
What's up with that? Isn't the pfuLockDown{App,
Cull, Draw} command supposed to lock the CPUs away
from other apps from disturbing the Performer
processes?
I'd appreciate any suggestions you may have.
Thanks,
Liem Lu
Logicon Technical Services, Inc.
P.O. Box 317258
Dayton, OH 45437 USA
llu++at++al.wpafg.af.mil
=======================================================================
List Archives, FAQ, FTP: http://www.sgi.com/Technology/Performer/
Submissions: info-performer++at++sgi.com
Admin. requests: info-performer-request++at++sgi.com
This archive was generated by hypermail 2.0b2 on Mon Aug 10 1998 - 17:55:27 PDT