Re: [jetty-dev] Improving performance of very large responses with Jetty

[Greg Wilkins <gregw@xxxxxxxxxxx>]

Aaron,

firstly you might want to try a SNAPSHOT release, or there should be
an M1 next week.
Increasing outputBufferSize is a good thing to do for dynamic content.
  How large depends on how many concurrent requests you expect and how
much memory you have.
But I think 64KB or 128KB is a reasonable place to start.

There are other JVM channel configurations that could be tweaked by
extending the connector and implementing the customise method.

cheers




On 11 October 2012 04:17, Aaron Daubman <daubman@xxxxxxxxx> wrote:
> Greetings,
>
> I'm using Jetty 9 M0 and am troubleshooting long response times,
> particularly for one app that potentially returns 10+Mb of dynamic
> content per-call.
> I am wondering where good starting points may be for tuning for
> large-response-body scenarios.
>
> I see that jetty.xml has the HttpChannelConfig section now, but am not
> sure of all of the parameters or how/if they would help.
> Should I be upping the outputBufferSize? If so, what would be a sane
> value (average response size)?
>
> Are there other settings I could/should tune that may help speed along
> these large responses?
>
> Thanks,
>       Aaron
> _______________________________________________
> jetty-dev mailing list
> jetty-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/jetty-dev