CODEWITHSUNDEEP
phpgrpchttp2
lshas
lshas

Reputation: 1731

php gRPC connections

I have a question I can't seem to find the answer to. We are building a gRPC microservice in Go, to serve our main application written in PHP. I am running some tests on one of the functions now, to see the performance.

My results indicate that setting up the connection takes about 2 seconds, but after that, each call takes less than a microsecond.

How does it work in a real-life application? Does it open one shared connection that is kept alive for a while, or does each request to our application have to open its own connection to the service?

If each request has to open its own connection, is it possible to get around this to get rid of the overhead that comes with establishing a new connection?

Upvotes: 3

Views: 1641

Answers (2)

Khepin
Khepin

Reputation: 949

The latest php-grpc extension will keep your connections around and re-use them between requests. Those are called "persistent" connections. A previous connection can be re-used if the set of parameters given to the connection constructor are exactly the same.

Source: php-grpc documentation: https://grpc.github.io/grpc/php/class_grpc_1_1_channel.html

By default, the underlying grpc_channel is "persistent". That is, given the same set of parameters passed to the constructor, the same underlying grpc_channel will be returned.

Upvotes: 1

rubens21
rubens21

Reputation: 801

What you need is called connection pool.

I found this PR https://github.com/grpc/grpc/issues/15426 after a short search on Google, but I am not sure if it is actually for pooling connections.

If you get able to create connections polls, you may just pick up one available connection and use for your request.

[EDITED]

I just found something that may work for your needs:

https://github.com/swoole/swoole-src#the-simplest-example-of-a-connection-pool

If you follow the example of the Redis connection pool you will be able to make a gRPC connection pool.

Upvotes: 3

Related Questions