[grpc-io] Using the certificate fetcher API

Hi, We are working on using the C++ implementation of gRPC and wanted to see what's the best way to implement certificate rotation. I was able to rotate certificates using the certificate fetcher callback API, but noticed that it's only available through the private headers of the core library.

[grpc-io] Re: Using the certificate fetcher API

Following up on this question, is there a plan for supporting the certificate fetcher API in the public facing headers? On Thursday, August 31, 2023 at 6:10:52 PM UTC-4 Amirsaman Memaripour wrote: > Hi, > > We are working on using the C++ implementation of gRPC and wanted to see > what's the be

[grpc-io] Re: Using the certificate fetcher API

Ho Luwei, Thanks for your response. We'd need to expand that API since the rotation of certificates must be controlled/guarded by a change of state in the system, and we may need to process the contents of the certificate files before loading them into memory for gRPC's consumption. My initial

[grpc-io] io_uring support for gRPC's C++ implementation

Hi, Are there any plans to add io_uring support (or other alternatives to reduce the number/frequency of system calls) to gRPC, in particular the C++ implementation? If so, is there a timeline for this work to land? Otherwise, is the idea rejected for any specific reason? -- You received this

[grpc-io] Re: Baseline overhead for C++ server

Thanks for sharing the link. I'm wondering if the issue referenced in this PR is addressed, and if the numbers reported for C++ are correct? In other words, should I expect ~260K QPS for running the streaming, secure `ping` benchmark against an 8 core

[grpc-io] Re: Baseline overhead for C++ server

Thanks again. Just to verify, we expect to see the C++ implementation to offer half of the throughput of the Go and Java implementations, providing a peak of 260K QPS on an 8 core server, correct? On Thursday, October 3, 2024 at 6:36:46 PM UTC-4 veb...@google.com wrote: > Those numbers look cor

Re: [grpc-io] Re: Baseline overhead for C++ server

ual QPS you'll see will > likely be much lower and the difference between C++ and Java/Go becomes > insignificant. The raw numbers you see from the benchmark should be correct. > > > On Thu, Oct 3, 2024 at 3:43 PM 'Amirsaman Memaripour' via grpc.io < > grpc-io@g

[grpc-io] Baseline overhead for C++ server

Hi folks, Are there any published latency numbers for the baseline overhead of a C++ ping server, using gRPC's CQs? I'm primarily interested in the per request CPU overhead of gRPC's RPC stack on the server-side, and if there are studies on tuning the number of polling threads and CQs to optimi

[grpc-io] Re: Baseline overhead for C++ server

Pinging in case this didn't show up in your radar :) On Tuesday, September 24, 2024 at 1:11:21 PM UTC-4 Amirsaman Memaripour wrote: > Hi folks, > > Are there any published latency numbers for the baseline overhead of a C++ > ping server, using gRPC's CQs? I'm primarily interested in the per req