@Joey this seems to be the case, with latency numbers now similar. I am still unable to conclude why the grpc streams numbers are ~1/2 of http requests. Please note I am using grpc streams as the number of requests since the lookup resources API is a server side streaming API and I create one stream for each request. Update#1 : Looks like it may be k6 who's causing the damage, will look more into it. https://github.com/grafana/k6/issues/1846 https://cdn.discordapp.com/attachments/844600078948630559/1327615929290592266/grpc-multiplexed.png?ex=6783b62f&is=678264af&hm=c8c833b1ebfb61ad5c92aab8ffdfc1a50785b43a47c55ce95b7cbe6d695d37f6& https://cdn.discordapp.com/attachments/844600078948630559/1327615929638457486/http-with-grpc-multiplexed.png?ex=6783b62f&is=678264af&hm=6b5eb14eebabe23882eb98e5f52ad45d9a44d76aed91097f5aed69e3d08d740f&