[Bf-committers] Thoughts on speeding up...
bfdeveloper at gmail.com
Wed Mar 23 23:19:36 CET 2005
Well, the problem is that Blender is currently a mainly single-threaded
application. Many of us have robust, dual CPU machines with support for
simultaneous multithreading. What should be possible is that Blender
computes the scene in the background, and as you edit the scene, it 'builds'
upon this current computation.
From: bf-committers-bounces at projects.blender.org
[mailto:bf-committers-bounces at projects.blender.org] On Behalf Of Alexander
Sent: Wednesday, March 23, 2005 3:10 PM
To: bf-blender developers
Subject: Re: [Bf-committers] Thoughts on speeding up...
On Wed, 23 Mar 2005, Austin Benesh wrote:
> Hi Ton,
> I was looking through your thread render code and got some ideas to help
> speed of Blender. What could be done is two threads could be created, one
> for interfacing and the other for rendering. Then, every time
> allqueue(REDRAWVIEW3D) is called, the scene could be "re-rendered" without
> actually drawing pixels and without sacrificing speed. I'm working on an
> implementation of this right now. Please tell me what's wrong with this
> idea, as I am sure there is something wrong.
It is an interesting idea, and the same idea I had a few days ago and
already proposed to Ton. It can be done, but it's some work.
BTW, I would have used it for also always providing a better preview
of the scene in the 3d views (an extension of shaded view).
| alexander ewering instinctive mediaworks
| ae[@]instinctive[.]de http://www[.]instinctive[.]de
Bf-committers mailing list
Bf-committers at projects.blender.org
More information about the Bf-committers