Any chance dgraph could support compression?
The RDF data that we send to the server can be compressed to less than 40% when gzipped. Given that upserts currently all require a query and then a mutation, the decreased throughput requirements should help significantly.
Are we talking about supporting reading of gzip compressed request body from the client?
Yep, the ability to send Gzip compressed strings through the various
clients, and for them to be read properly on dgraph server's side.
On Mon, 19 Mar 2018 at 22:02, Pawan Rawal notifications@github.com wrote:
Are we talking about supporting reading of gzip compressed request body
from the client?—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/dgraph-io/dgraph/issues/2241#issuecomment-374397079,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACKSZpS8vSaTZHI-UZV7mDabyNQxCKlLks5tgCrqgaJpZM4Sv9eY
.>
Thanks,
Vlad
Very useful indeed, especially with loads of requests and data going in and out of Dgraph! Also economic with ingress and egress in cloud providers.
Grpc should already support this. Let's see how best we can bring it in.
Should dgraph also support compression over HTTP? That is, handle the Accept-Encoding and Content-Encoding headers.
Most helpful comment
Yep, the ability to send Gzip compressed strings through the various
clients, and for them to be read properly on dgraph server's side.
On Mon, 19 Mar 2018 at 22:02, Pawan Rawal notifications@github.com wrote:
Thanks,
Vlad