One of the advantages of using the X double buffer extension or XRender or something like that is you don't need to send raster image data over the network. You're still sending ordinary drawing commands, and it's the server that accumulates the results into a pixmap somewhere.
If it is slow for you, you can turn off the new stuff:
(modify-frame-parameters nil '((inhibit-double-buffering . t)))But why inhibit-double-buffering and not just the simple no-double-buffering?
(I hope this change doesn't make it run crappily in XQuartz! X-Windows programs that do double buffering draw to an offscreen buffer often perform really poorly, poorly enough that I'd definitely rather have the flicker, not least because I don't mind the flicker too much anyway.
(I assume a lot of them have a client-side pixmap that's written to manually, and then has to be sent over the network link. )