Hello:

I've attached my current winmgr.conf.  Other responses inline:

> Please provide us with your winmgr.conf configuration file to better help us 
> determine what the composition manager might be trying to do.
> 
> Other questions:
> 
> What is the EGL_SWAP_BEHAVIOR set to ? If EGL_BUFFER_PRESERVED is requested 
> this will add to the amount of work EGL has to do when swapping buffers.

EGL_SWAP_BEHAVIOR is set to EGL_BUFFER_DESTROYED

> 
> What are the values for KD_WINDOWPROPERTY_BUFFER_SIZE_QNX, 
> KD_WINDOWPROPERTY_SOURCE_SIZE_QNX, KD_WINDOWPROPERTY_SOURCE_POSITION, 
> KD_WINDOWPROPERTY_SIZE, and KD_WINDOWPROPERTY_POSITION_QNX ?

KD_QNX_WINDOWPROPERTY_SOURCE_SIZE is 780,380
KD_QNX_WINDOWPROPERTY_SOURCE_POSITION is 0,0
KD_WINDOWPROPERTY_SIZE is 780,380
KD_QNX_WINDOWPROPERTY_POSITION_QNX is 0,0

> 
> What is the value of EGL_RED_SIZE, EGL_BLUE_SIZE, EGL_GREEN_SIZE, and 
> EGL_ALPHA_SIZE of the EGLConfig that your application is using to create the 
> window surface ?

They are 8,8,8,8 respectively.

> 
> Note that using the composition manager does have a performance impact, even 
> if compositing is disabled. In this case, EGL is forced to wait for renders to
>  complete before sending a post message to the composition manager. This 
> eliminates any potential overlapping of CPU and GPU and causes the GPU to be 
> idle for some time, unless other applications are running in parallel. 
> Consequently, free running frame rates of applications without composition 
> manager will always be equal or higher than their composition manager 
> counterpart. This can be overcome with triple buffering, which might be added 
> to our EGL at some point.

Yup... I expected some performance impact, but not close to an order of magnitude. I have run that same test image 
through a simple gf blitting directly to a layer (without io-winmgr running) and get about 65 fps on that.

So, overall I have several applications all running at the same time using CM.  Aside from some transitions putting 
application windows on and off the screen, when an application window is visible, it owns the entire displayable area 
(800x480).  Obviously my little image test program is only creating a window as large as the image it is displaying, so 
that may not count.  Actually, I just ran a test with a full-screen sized image (and window) and it's fps using CM and 
openvg is about 4.5 fps, and with just a native gf it is about 54 fps.