Mark,
On 7/24/24 02:27, Mark Thomas wrote:
On 23/07/2024 21:30, Christopher Schultz wrote:
Mark,
On 7/23/24 13:13, Mark Thomas wrote:
Prompted by some folks at $dayjob, I have been looking at the
performance of Tomcat's HTTP/2 implementation using [1]
Initially, I was seeing ~79k req/s.
Re
On Wed, Jul 24, 2024 at 8:31 AM Mark Thomas wrote:
>
> On 23/07/2024 21:30, Christopher Schultz wrote:
> > Mark,
> >
> > On 7/23/24 13:13, Mark Thomas wrote:
> >> Prompted by some folks at $dayjob, I have been looking at the
> >> performance of Tomcat's HTTP/2 implementation using [1]
> >>
> >> In
On 23/07/2024 21:30, Christopher Schultz wrote:
Mark,
On 7/23/24 13:13, Mark Thomas wrote:
Prompted by some folks at $dayjob, I have been looking at the
performance of Tomcat's HTTP/2 implementation using [1]
Initially, I was seeing ~79k req/s.
Restoring lazy init for the StreamInputBuffer i
Mark,
On 7/23/24 13:13, Mark Thomas wrote:
Prompted by some folks at $dayjob, I have been looking at the
performance of Tomcat's HTTP/2 implementation using [1]
Initially, I was seeing ~79k req/s.
Restoring lazy init for the StreamInputBuffer increased that to ~106k
req/s.
O_O
Moving the
On Tue, Jul 23, 2024 at 7:15 PM Mark Thomas wrote:
>
> Prompted by some folks at $dayjob, I have been looking at the
> performance of Tomcat's HTTP/2 implementation using [1]
>
> Initially, I was seeing ~79k req/s.
>
> Restoring lazy init for the StreamInputBuffer increased that to ~106k req/s.
>
Prompted by some folks at $dayjob, I have been looking at the
performance of Tomcat's HTTP/2 implementation using [1]
Initially, I was seeing ~79k req/s.
Restoring lazy init for the StreamInputBuffer increased that to ~106k req/s.
Moving the HttpParser from Processor to Protocol increased that
