Hello, There is ghz (https://github.com/bojand/ghz). It's a tool a made a little while ago (and still maintain) for benchmarking and load testing gRPC services. It is inspired by hey and grpcurl. Hopefully it can be useful for your use case. If you have any problems feel free to create GitHub issues with relevant information.
Alternatively there seem to be few other approaches from some quick research; but I have not used any of these: Supposedly Gatling can be used with gRPC: https://medium.com/@georgeleung_7777/load-testing-grpc-services-with-gatling-990025c77055 There is a library for making your own test: https://github.com/emicklei/hazana Buoyant.io seems to have some kind of stress-test utility: https://github.com/BuoyantIO/strest-grpc Good luck! On Wednesday, 5 December 2018 20:12:41 UTC-4, AD wrote: > > How do folks approach load testing of gRPC services? Are there any > recommendations for tools that can be used for load testing gRPC services? > > I'm was also exploring the possibility of using a generic h2 load testing > tool (e.g. https://github.com/rakyll/hey/ and > https://github.com/tsenart/vegeta) by using serialized gRPC payload. > However, I'm drawing a blank on how to go about serializing h2 requests > for gRPC calls. > > -- You received this message because you are subscribed to the Google Groups "grpc.io" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/grpc-io. To view this discussion on the web visit https://groups.google.com/d/msgid/grpc-io/96d246d5-554d-47eb-afe6-092a66aa92d7%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
