users@grizzly.java.net

Re: Parallel writes revisited: bug or me?

From: Ryan Lubke <ryan.lubke_at_oracle.com>
Date: Tue, 07 Feb 2012 10:23:54 -0800

On 2/6/12 2:25 PM, Matthew Swift wrote:
> Awesome - thanks for the info. :-)
>
> I'll take a look at this tomorrow (getting late here now) and come
> back with any questions I have, but it looks pretty straightforward
> from what you describe.
Great! And just in case it was missed, it would require migrating to
2.2.1.
There are some API changes in that release, FYI.
>
> Cheers,
>
> Matt
>
> On 6 February 2012 23:00, Ryan Lubke <ryan.lubke_at_oracle.com
> <mailto:ryan.lubke_at_oracle.com>> wrote:
>
> Further details...
>
> <snip>
>
> Presumably there's some sort of bounded write queue.
> </snip>
>
> In addition to the PushBackHandler, there are a couple of ways to
> configure the size of the queue.
>
> See: AsyncQueueWriter.setMaxPendingBytesPerConnection(int) [1]
>
> By default, the queue will be limited to four times the size of
> the socket write buffer size.
>
> This value may be initially set via
> TCPNIOTransportBuilder.setMaxAsyncWriteQueueSizeInBytes(int) [2].
>
>
>
> [1]
> http://java.net/projects/grizzly/sources/git/content/modules/grizzly/src/main/java/org/glassfish/grizzly/asyncqueue/AsyncQueueWriter.java?rev=15de8fef0a4f138636e222f861ae6cb1fcf111f9
>
> [2]
> http://java.net/projects/grizzly/sources/git/content/modules/grizzly/src/main/java/org/glassfish/grizzly/nio/transport/TCPNIOTransportBuilder.java?rev=15de8fef0a4f138636e222f861ae6cb1fcf111f9
>
>