Meshery: [Performance] Adding support for gRPC testing
Current Behavior
Through the load generator interface (an area of extensibility) in Meshery, fortio's ability to generate HTTP load has long been supported.
Desired Behavior
With many service-to-service interactions being of gRPC, Meshery should also support generation of gRCP load and its performance testing.
Related
- https://github.com/layer5io/meshery/issues/133 - support for TCP load generation
girishranganathan
All 7 comments
Doing some release planning now... @sakomws is this one that you're intending to take on?
leecalcote
on 15 Jun 2019
Hi @leecalcote i will bring GKE cluster and start working on it. Sorry got distracted a bit.
sakomws
on 18 Jun 2019
@sakomws any progress to report here?
leecalcote
on 23 Jul 2019
@ldemailly we'll be enlisting fortio's capability here. 馃憤
// @kushthedude @durgesh96751 @prateeksahu @DavidCPorter @swhsiang @mum4k @suryadu @mandarjog
leecalcote
on 19 May 2020
Knock Knock! @kushthedude checking in for situation report.馃槂
PluckyPrecious
on 15 Aug 2020
Way of distinguishing between protocols?
- grpc://funtionName(param 1, "bob", true)
- need to use advanced headers inside payload
- tcp://192.168.1.15:3000/endpointname
- http://
- https://
leecalcote
on 22 Oct 2020
side note I use tcp:// in newer fortio for tcp load testing from the web UI to distinguish from (default) http and from grpc (which has a seperate flag but maybe the above is better)
ldemailly
on 23 Oct 2020
Related issues
leecalcote
路
4Comments
leecalcote
路
4Comments
leecalcote
路
4Comments
leecalcote
路
3Comments
sakomws
路
4Comments
Most helpful comment
side note I use tcp:// in newer fortio for tcp load testing from the web UI to distinguish from (default) http and from grpc (which has a seperate flag but maybe the above is better)