[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Painter Fuzzy Node in github
From: |
David Chisnall |
Subject: |
Re: Painter Fuzzy Node in github |
Date: |
Thu, 18 Dec 2014 12:56:19 +0100 |
On 18 Dec 2014, at 10:52, Johan Ceuppens <address@hidden> wrote:
> With this in mind, which part do you think can be sped up by applying AI
> techniques?
>
>
> Lots, it comes down to start with any window subhierarchy such as subviews,
> CALayers, anything which get rendered even if it is composited by the GPU as
> the AI idles the caching and full bottoms up layering/hierarchying the
> rendering system with its own data structures such as a tree or graph (a tree
> for a decision tree a graph for fuzzy network and a list for fuzzy sets.)
You can't speed up the final render step, because the GPU *has to composite all
layers*. Attempts to do partial compositing and merging of the result are
slower than doing a full composite.
Please don't conflate views and layers. A view draws when it needs to change.
A layer contains a cache and does not cost anything to redraw. When the views
are not being updated, the rendering is basically free.
You do not make things faster by adding complexity to simple things.
David
--
This email complies with ISO 3103
- Re: Painter Fuzzy Node in github, (continued)
- Re: Painter Fuzzy Node in github, Ivan Vučica, 2014/12/17
- Re: Painter Fuzzy Node in github, Johan Ceuppens, 2014/12/18
- Re: Painter Fuzzy Node in github, David Chisnall, 2014/12/18
- Re: Painter Fuzzy Node in github, Johan Ceuppens, 2014/12/18
- Re: Painter Fuzzy Node in github, Johan Ceuppens, 2014/12/18
- Re: Painter Fuzzy Node in github, Ivan Vučica, 2014/12/18
- Re: Painter Fuzzy Node in github, Johan Ceuppens, 2014/12/18
- Re: Painter Fuzzy Node in github, Ivan Vučica, 2014/12/18
- Re: Painter Fuzzy Node in github, Johan Ceuppens, 2014/12/18
- Re: Painter Fuzzy Node in github, Johan Ceuppens, 2014/12/18
- Re: Painter Fuzzy Node in github,
David Chisnall <=