Overhead of X?

[Bilderbeek, Manuel]

Hi,

> X does a little more than just a memset() of the enitre framebuffer.
> Filling the entire framebuffer with just one solid color is 
> nothing that
> the solid fill code in fb (that's what you are using unaccelerated) is
> really optimized for. Therefore it will perform some tests 
> and operations
> that are not required for this particular operation.

Would all those tests take so much CPU that it makes it 3 times slower?
So, 2/3 of the time is used for calculations and checks?
After all, the fill code is just supposed to fill a solid rectangle, so
the filling itself should be comparable. Or not?

> This doesn't seem to be a very common use either.

Isn't an application mainly painting filled rectangles, copying images
and drawing lines?
 
> Furthermore memset() is ususally higly optimized for your 
> architecture.

If the fb fill routine would use memset, would that matter? (I don't
know if it does that, but I don't see why it couldn't...)
 
> This seems to be a poor comparison.

How can I make it better?

Maybe running the application in the root window might help? (Could save
some checks!)
How would I do that, anyway? (Run a Java app in the root window...)

--
Kind regards,

Manuel Bilderbeek

This message and attachment(s) are intended solely for the use of the addressee and may contain information that is privileged, confidential or otherwise exempt from disclosure under applicable law.  
If you are not the intended recipient or agent thereof responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution, or copying of this communication is strictly prohibited.  
If you have received this communication in error, please notify the sender immediately by telephone and with a "reply" message.  
Thank you for your cooperation.