Re: Frame Freeze

New Message Reply Date view Thread view Subject view Author view

Rob Jenkins (robj++at++quid.engr.sgi.com)
Fri, 3 Apr 1998 13:26:58 -0800

We're running 2 separate 'perfly' executables on an 8 processor ONYX.
> We've bound each perfly to it's own processor using the runon command on
> the command line. We also have several other processes running on all
> of the other processors. The display freezes for 1-3 seconds quite
> frequently. We've tried taking out the runon command and letting the
> perfly run freely on whatever processor it chooses. This does not stop
> the freezing display. We've cut the frame rate down to 20.0 HZ and that
> helped the frequent freezes, but it makes the display more jumpy. Does
> anyone have any suggestions on how to avoid the freezing display?
>
> Should we try to bind the Draw processes to their own processors, and
> put the APP and CULL somewhere else?
>
> Thanks in advance for any help.
>
> Suzie
>
> --Press any key to go on.--
>

Suzie

Sounds like something is fighting for CPU time. I would suggest setting
PFNFYLEVEL 6, look at the Performer Process State messages to see what pids run
on what CPUs then use par -rQQtN where N is enough seconds to catch a freeze (
you'll need to run that as root ). This should show you what processes run on
which CPUs with what priority and also what is switching them on/off CPUs. The
if you see obvious conflicts you can try moving things around. Make sure you
have the latest recommended patchset too to get the latest kernel roll up patch
( see www.sgi.com/support for patchsets ).

Cheers
Rob

-- 
________________________________________________________________
Rob Jenkins mailto:robj++at++sgi.com
Silicon Graphics, Mtn View, California, USA
=======================================================================
List Archives, FAQ, FTP:  http://www.sgi.com/Technology/Performer/
            Submissions:  info-performer++at++sgi.com
        Admin. requests:  info-performer-request++at++sgi.com

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:57:12 PDT

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