Some more tests and found lazy loading of modules in other areas,
gives good speedup on cold start.
Times don't compare to last tests because I disabled some options
(BGE, FFMPEG etc).
I did lazy importing of modules:
traceback, shutil, time, math and pydoc
I also removed 'collections' import
-committers] Blender Startup Time
To: bf-blender developers bf-committers@blender.org
Received: Sunday, February 27, 2011, 8:23 AM
Some more tests and found lazy
loading of modules in other areas,
gives good speedup on cold start.
Times don't compare to last tests because I disabled some
Barton ideasma...@gmail.com wrote:
From: Campbell Barton ideasma...@gmail.com
Subject: Re: [Bf-committers] Blender Startup Time
To: bf-blender developers bf-committers@blender.org
Received: Sunday, February 27, 2011, 8:23 AM
Some more tests and found lazy
loading of modules in other areas
On Sat, Feb 26, 2011 at 4:56 AM, Martin Poirier the...@yahoo.com wrote:
--- On Fri, 2/25/11, Campbell Barton ideasma...@gmail.com wrote:
I think most of this problem can be fixed by doing
lazy-importing.
Where a scripts will only register its classes on startup
but not
actually load the
I think It's important to note that we do have a splash screen, and it will
take a certain amount of time to click through that. So we can just change
the load order (Since the overall load time is not that significant), making
Blender itself load as fast as possible, and everything else that is
Hi,
j.jay...@gmail.com (2011-02-27 at 0740.30 +0900):
I think It's important to note that we do have a splash screen, and it will
take a certain amount of time to click through that. So we can just change
the load order (Since the overall load time is not that significant), making
Blender
Today I took some time to look at how much slower blender 2.5x is then
2.4x, and possible ways to make it faster.
http://wiki.blender.org/index.php?title=User:Ideasman42/BlenderStartup
Or just jump to conclusions
http://wiki.blender.org/index.php?title=User:Ideasman42/BlenderStartup#Conclusions
Hi,
On my slow PPC system, debug build, the full 'cold' startup takes
about 5 seconds, of which 3.5 is being spent in BPY_python_start()
On second and successive runs it's 1.2s for Python. Without netrender
only saves 0.1 sec... total about 2.5 seconds.
Interesting is that then quite some
Am 25.02.2011 14:00, schrieb Campbell Barton:
Today I took some time to look at how much slower blender 2.5x is then
2.4x, and possible ways to make it faster.
[...]
Other suggestions for improving startup time welcome!
My suggestion: Don't care about these 5 seconds ;-)
How often do I start
On Feb 25, 2011, at 8:53 PM, Carsten Wartmann wrote:
How often do I start Blender a day? If I am lucky ONE time. If not the
next starts are warm starts.
It is different for devs who need to restart constantly to see if got a bug
fixed etc :)
But a good point anyway, even there 5secs is not a
Blender still has blazing fast startup (compared to any app). I'd be really
happy keeping it that way, but I do agree that wether it takes three, four or
five seconds seems quite irrelevant.
Mats Holmberg, ArtFlow
3D-Animation / 3D-Graphics / Airbrush Art Supplies
mobile +358 (0) 40 1920382
Hi,
ideasma...@gmail.com (2011-02-25 at 1300.36 +):
One thing I found was disk speed on a 'cold start' to be the major bottleneck,
Does anyone know some way we could asynchronously cache certain files
on load so when they are needed it wont lag so much?
When it says function body removed,
@Carsten, others on IRC said this too - that we are doing ok compared
to others and should not worry about startup times.
The thing is, since python was added we have not made _any_ effort to
make blender efficient for startup, importing modules without worrying
of the side-effect or trying to
13 matches
Mail list logo
