[Xcb] profiling and performance

[Ian Osgood]

On May 3, 2006, at 9:58 AM, Vincent Torri wrote:

>
> Hey,
> Jamey wrote:
>> The only reply you get with any interesting frequency is for
>> GetInputFocus, presumably for XCBSync. The more XCBSync calls you can
>> remove without changing the behavior of your program, the higher its
>> throughput will be. Understanding when you can remove XCBSync  
>> calls is
>> hard though.
>
> Oulaaa, I don't know at all when removing them :D I know that there  
> is a
> call that I can remove. That's all.
>
> Same for XCBFlush ?

Is there a guide for when one should use Flush or Sync?  I've  
converted all Syncs to Flushes in my code, to no ill effect.  And  
then I remove the Flushes when I can.

In fact, is there a reason XCBSync is part of the core API?  It isn't  
used internally, not even by Xlib/XCB, and only uses other public  
functions, so it seems to be more of a candidate for a utility  
library.  That would also give the hint that this is NOT a function  
you should be using all over the place.

Ian