Blogpost: grapesy: industrial strength gRPC library for Haskell - Well-Typed: The Haskell Consultants
Library: grapesy: Native Haskell implementation of the gRPC framework
32 Likes
Great stuff. I have two questions, one serious one silly.
-
About the performance, “it’s on par with java” GitHub - well-typed/grapesy: Native Haskell gRPC client and server based on `http2` How is it that concurrent performance is 3x lower on Linux comparing to Java version?
-
Is the name “grapesy” simply a phonologically humourous take of “grpc”, or it has some more meanings to it?
(edit), I found a page for more performance comparison, if relevant, 2024-09-20 i5-6600K (4) @ 3.90 GHz, 16GB · LesnyRumcajs/grpc_bench · Discussion #475 · GitHub
3 Likes
- That’s a fair question. It is difficult to disentangle the performance of grapesy-the-library from the performance of the overall network stack (including grapesy, and everything below). We felt that the sequential performance was the best measurement that isolated the effects of message encoding, setting up the connection etc. The performance of the concurrent version could be down to all kinds of things – including, of course, grapesy itself. It’s certainly worth looking into, if this is an actual issue for deployment (though I suspect it won’t be).
- No meaning, just a pronunciation of “gRPC”
-E
7 Likes