Hi all,
The issue is the same one that Jan brought up on an earlier Solaris support
PR: "is there a way to setup automated testing for this? If not, it is
likely that the build will get broken soon. Note that our test farm doesn't
provide any solaris machines to test with." We're not in a position
Added an assignee to the PR. This is low priority so please bear with the
delay.
On Thursday, August 9, 2018 at 12:27:20 AM UTC-7, Jasper Siepkes wrote:
>
> Hi all!
>
> There is a PR for adding Solaris support in gRPC (
> https://github.com/grpc/grpc/pull/15926 ). Is there a chance for such
> s
The single connection time for the whole process is about 2.75 sec, and the
multiple connection time is about 3.5 sec. I run this test multiple times,
and the single connection is always a bit faster than the multiple
connections
On Saturday, August 18, 2018 at 8:37:22 PM UTC-7, Srini Polavarap
Hi Srini,
The way how I do it:
for single connection:
1. send 1 request via request StreamObserver, to let initial connection
established
2. start the timer, send 1 requests
3. end the timer when see all results from the response
StreamObserver.onNext() that the client passed to the serve
There is some flakiness in bazel tests. Please file an issue on github and
provide the steps in detail to reproduce this.
Thanks.
On Friday, August 17, 2018 at 3:16:13 PM UTC-7, Abhishek Parmar wrote:
>
> I have a weird problem with one of my unit tests that is using streaming
> grpc. The test
Could you provide some stats on your observation and how you are measuring
this? Two streams sharing a connection vs. separate connections could be
faster due to these reasons:
- One less socket to service: less system calls, context switching, cache
misses etc.
- Better batching of data from di
