Re: Is there any way to intercept or generate protocol to an in-memory buffer?

The overhead of doing separate XShmPutImages should be minimal. If you're
seeing performance issues from that, you might be using the XCB Image
library: you probably should look there for optimizations: I know that
little care went into trying to make it fast back when it was written.

On Tue, Dec 26, 2017 at 12:11 PM Clemens Eisserer <[email protected]>
wrote:

> Hi there,
>
> I am currently trying to solve a performance problem in Java2D's
> xrender backend.
> What I actually would like to do is to defer the actual command
> submission to the x-server in order to batch many small XPutImages to
> one large XShmPutImage.
> I could do this in my own code (log API calls to an application
> managed buffer and call the coresponding Xlib/xcb functions later from
> within a large protocol-decoding switch statement). However I wonder
> if there isn't a more efficient way, given the fact that X's network
> transparency introduces some kind of defering anyway.
>
> Is there any way to intercept the protocol before it is sent to the
> X-Server?
> Or in case interception is not supported, is there a way to let xcb
> generate all protocol to a user-accessible / user-controlled buffer
> and submit it manually to the x-server?
>
> Thank you in advance and best regards, Clemens
> _______________________________________________
> Xcb mailing list
> [email protected]
> https://lists.freedesktop.org/mailman/listinfo/xcb

_______________________________________________
Xcb mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/xcb