Re: [grpc-io] Consequences for increasing flowControlWindow?

['Eric Anderson' via grpc.io]

I'd suggest increasing the number only if you can show the result of
(bandwidth * RTT) is higher than the current value (1 MB). We'd really like
to be auto-tuning this value, but because we use such a high default value
it's not been a huge burden. Go and C actually already auto-scale. And Java
even has the code, but we need to fix a few edge cases to avoid upsetting
some other HTTP/2 implementations.

Most networks only need 64 KB. Some cloud-type networks need 1 MB when
you're "slightly far" away from the remote side. And then something like an
intercontinental transfer on a nice/fat network might need 4 MB. Note this
value only impacts receiving; you want to set it on the receiver, or on
both sides if both sides receive large amounts.

On Tue, Dec 5, 2017 at 2:41 PM,  wrote:

> I am using NettyChannelBuilder
> 
> on my client and NettyServerBuilder
> 
> on my server. I notice when I increase the flowControlWindow option on the
> client and server, e.g:
>
> .flowControlWindow(NettyServerBuilder.DEFAULT_FLOW_CONTROL_WINDOW * 10)
>
>
> I notice higher throughput ability in my stream, I believe this is because
> it increases the TCP flow control window so more bytes can be
> in-flight/buffered on each side.
> However are there any possible downsides to increasing this value? What
> actually happens on a lower level? Does it just increase the memory
> allocated to the internal buffers?
>
> Thanks 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 grpc-io+unsubscr...@googlegroups.com.
> To post to this group, send email to grpc-io@googlegroups.com.
> Visit this group at https://groups.google.com/group/grpc-io.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/grpc-io/93e6301e-0a8b-4201-991b-a0d7865ea068%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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 grpc-io+unsubscr...@googlegroups.com.
To post to this group, send email to grpc-io@googlegroups.com.
Visit this group at https://groups.google.com/group/grpc-io.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/grpc-io/CA%2B4M1oPg53S%2BZHzpZL5WUBC3_FjZ3Nwhwei7SmUu4ARnj6kATQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.


smime.p7s
Description: S/MIME Cryptographic Signature

[grpc-io] Consequences for increasing flowControlWindow?

[thas . himal]

I am using NettyChannelBuilder 
 
on my client and NettyServerBuilder 
 
on my server. I notice when I increase the flowControlWindow option on the 
client and server, e.g:

.flowControlWindow(NettyServerBuilder.DEFAULT_FLOW_CONTROL_WINDOW * 10)


I notice higher throughput ability in my stream, I believe this is because 
it increases the TCP flow control window so more bytes can be 
in-flight/buffered on each side. 
However are there any possible downsides to increasing this value? What 
actually happens on a lower level? Does it just increase the memory 
allocated to the internal buffers? 

Thanks 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 grpc-io+unsubscr...@googlegroups.com.
To post to this group, send email to grpc-io@googlegroups.com.
Visit this group at https://groups.google.com/group/grpc-io.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/grpc-io/93e6301e-0a8b-4201-991b-a0d7865ea068%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.