No subject

Fri Feb 27 10:16:53 PST 2009

  With xcb every write (in _XFlush) is followed by a read
  (_XEventsQueued) which is the cause of the very poor performance. The
  read usually returns EAGAIN because there is nothing to be read, but
  it is a severe performace hit anyhow.  And why _XEvenetsQueued/read is
  being called when select/poll has previously returned indicating only
  a single file descriptor was ready is anybody's guess.

Can you provide some insights into what causes this issue?

These seem to all (maybe?) be reports of the same issue:


More information about the Xcb mailing list