Re: Performance problems with Performer

New Message Reply Date view Thread view Subject view Author view

leif.stubbfalt++at++enator.se
Sat, 30 Jan 1999 13:28:33 +0100


marko.aho skrev:
>
> Hi
>
> You wrote into Info-Performer mailing list:
>
> >Hi,
> >We are experiencing performance problems with Performer at platform
> >O2 R5k / IRIX 6.5.2. Our application is now running super slowly !
>
> >It seems to be a lot of kernel mode execution going on.
>
> I saw this happen to me last week under the same conditions. I have O2 R5k
> and had installed 6.5.2 a few days earlier.
> I was developing new db-loader for Performer in my own program. I did many
> experimentals with statistics and
> refresh rates with xscreen. And had multiple program crashes too.
> Gradually during the day the performance dropped down so at first I did not
> even notice it.
> Eventually I was noticed that something was wrong.
> When I looked at the gr_osview there was lots of system process going on.
> Still top did not report any process eating my resources.
>
> After a while of pondering I did the old trick I learned back in
> Windows-world: I restarted my machine.
> That cleared the overprocessing.
>
> I know, I know, with Unix you should not be forced to restart your machine
> even every year or so :-)
>
> Still now it works fine. I have 25Hz with GUI in perfly without a model and
> 37.5 Hz with the GUI off.
>
> Unfortunately this does not say which caused the original problem should
> this happen again.
>
> Regards
> Marko Aho
> Finnish Broadcasting Company
> marko.aho++at++yle.fi

Thanks for Your mail, Marko

I'll send this further to the Performer mailing list. Maybe some clever
guy can give us a hint of whats going on, with help of Your mail. By the
way, I have reported this problem to SGI (Sweden call SE08591), ten days
ago, but I haven't got any solution/workaround yet.

Regards
Leif


New Message Reply Date view Thread view Subject view Author view

This archive was generated by hypermail 2.0b2 on Sat Jan 30 1999 - 04:28:46 PST

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