lujiajing1126 commented on pull request #7495: URL: https://github.com/apache/skywalking/pull/7495#issuecomment-908846889
> > currently, the banyandb-java-client depends on our apm-datacarrier and queue the requests ourselves, I think the gRPC itself must have queue internally and know when is the best time to flush the requests. > > Let me get to this. gRPC and netty have internal queue, but it is for direct memory for sending, which can't avoid OOM :) We have suffered those years ago. BTW, I've recently found a project, https://github.com/salesforce/reactive-grpc. As I understand, according to the document, this project can properly handle the so-called back-pressure issue which is similar to what we provide thru `apm-data-carrier`. And it seems to be more capable since it is deeply integrated to the transport layer, i.e. HTTP/2 flow control. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: notifications-unsubscr...@skywalking.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
