[FusionDev] Compiz-manager sloweness (Was: Release)

[Alyssa Hung]

Kristian Lyngstøl wrote:
> Please remove the parts of the e-mail you are not using when quoting,
> to keep the thread clean.
> 
> On 8/11/07, Sam Spilsbury <smspillaz at gmail.com> wrote:
>
>> NOTE : The autostart slowness might be caused by the fact that it's trying
>> to kill metacity while it's starting.
> 
> It doesn't, it just uses --replace. There is a built in delay for the
> decorator, set to 5 seconds by default. Can you try configuring this
> to, say, 1 second and see if this is what you are seeing?
> 
> I still need answers to the first questions too:
> 
> 1. Is it consistently slow
> 2. When using verbose, is there a specific test that's slow?
> 3. Is it slower at the first run, or also slow after it has saved the
> results of the test too?
> 
> Compiz-manager only runs tests once in a normal setup, which would
> make it considerably FASTER than pretty much anything that doesn't, so
> I need to know the answers to these questions to determine the reason
> for the slowness.
> 
> I would also very much like to get confirmations from others.

As far as I know, many users are referring exactly to the 5-second
decorator startup delay when they say that compiz-manager is slow.
Compiz is now capable of auto-starting a decorator, configurable in
ccsm->Window Decoration->Command, and fusion-icon uses the
compizconfig-python interface to interact with this setting to remove
the need for a startup delay.

Older versions of fusion-icon used compiz-manager -r to find the 
recommended startup environment and arguments, but it hasn't been doing 
that for at least a month. compiz-manager -f -v -d (ignore cached 
config, verbose, dry run) is extremely fast on my computer, so unless 
some additional processing happens between these messages:

Exporting: __GL_YIELD=NOTHING
Executing: compiz --loose-binding --sm-disable --replace ccp

And Compiz actually starting, I'm not sure what may be causing the 
perceived slowdown aside from the 5 second decorator startup delay.