Or is there any way to use sync server not to blocking each insert request? 
as the above, server insert throughput doesn't go well with #thread when I 
use apache thrift as the same manner

2019년 6월 21일 금요일 오후 4시 14분 57초 UTC+9, [email protected] 님의 말:
>
> Hi there,
>
> I want to use my service as threaded server for handling each request 
> concurrently.
>
> But I only see the examples of threaded server of which service use just 
> one rpc methods.
> 1) 
> https://github.com/grpc/grpc/blob/v1.21.0/examples/cpp/helloworld/greeter_async_server.cc
> 2) 
> https://github.com/grpc/grpc/blob/master/test/cpp/end2end/thread_stress_test.cc
>
> I could see the way how to handle the requests with Queue, but both 
> examples use a single type of request and reply.
> But how can I handle the multiple types of rpc requests in service and 
> relevant responses like that way?
>
> Is there any example or recommended way to use async server?
> I'm now using the sync server as the 
> https://github.com/grpc/grpc/blob/v1.21.0/examples/cpp/helloworld/greeter_server.cc
>  example 
> like below.
>
> ServerBuilder builder;
> builder.AddListeningPort(server_address, 
> grpc::InsecureServerCredentials());
> builder.RegisterService(&service);
> std::unique_ptr<Server> server(builder.BuildAndStart());
>
> I'm looking forward to your help.
> Thanks a lot in advance! :)
>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/grpc-io/4c804f61-4708-4176-995c-25ccd1c1e413%40googlegroups.com.

Reply via email to