Angus Dorbie (dorbie++at++bitch.reading.sgi.com)
Fri, 3 Nov 1995 17:59:36 +0100
But you do want to mix compute tasks with rendering to use the CPU when
the graphics pipe is busy doing other things like clearing the screen or
writing lots of pixels. The last thing you want to do if running single
threaded is do a large block of computations in one go, unless it's after
a really heavily pixel limited operation like drawing your sky polygon, or
you can afford it because of rounding to your swapinterval.
I'd stick to the graphics callbacks for GL & spread the load of any
compute, where possible. But life would be easier for you if you assume
youre always going to run single threaded.
On Nov 3, 12:30pm, Lionel Maiaux wrote:
> Subject: Re: Mono or Multi-process ?
> Hi Angus,
>
> On Nov 3, 11:08am, Angus Dorbie wrote:
> > Subject: Re: Mono or Multi-process ?
> > You should run single process.
> >
> > The idea is to avoid your app_cull scheduling with your draw with
> > unfortunate consequences. If you are running single threaded you
> > have better control when your cpu is busy with app & cull to
> > minimise the impact upon graphics performance. You only have the
> > rest of unix to worry about.
> >
> > --
> > Angus Dorbie,
> > Silicon Graphics Ltd, UK
> > dorbie++at++reading.sgi.com
> >
> >-- End of excerpt from Angus Dorbie
>
> Ok, I will use single process,
> but must I take care about mixing graphic and non graphic tasks or not ???
> I suppose I should not take care about it if the length of the pipeline is
big
> enough to avoid my process to wait.
>
> (This question is not limited to Performer because I use a lot of IRIS GL
> calls in my application)
>
>
>
>
>-- End of excerpt from Lionel Maiaux
-- Angus Dorbie, Silicon Graphics Ltd, UK dorbie++at++reading.sgi.com
This archive was generated by hypermail 2.0b2 on Mon Aug 10 1998 - 17:52:00 PDT