Re: HTTP/2 optimizations and edge cases

2016-06-15 13:27 GMT+02:00 Mark Thomas : > On 13/06/2016 21:05, Rémy Maucherat wrote: > > My conclusion is that some sort of optional mechanism should be added. > > Makes sense to me. How did you implement this for your testing? > > I'm not happy about it so I added a BZ to

Re: HTTP/2 optimizations and edge cases

On 13/06/2016 21:05, Rémy Maucherat wrote: > 2016-06-03 17:36 GMT+02:00 Mark Thomas : > >> On 03/06/2016 15:59, Rémy Maucherat wrote: I am not talking about a limit on concurrent streams where things are >> being >>> refused (and this is exposed through the settings),

Re: HTTP/2 optimizations and edge cases

2016-06-03 17:36 GMT+02:00 Mark Thomas : > On 03/06/2016 15:59, Rémy Maucherat wrote: > >> I am not talking about a limit on concurrent streams where things are > being > > refused (and this is exposed through the settings), rather on streams > which > > are effectively being

Re: HTTP/2 optimizations and edge cases

On 05/06/2016 18:28, Christopher Schultz wrote: > Can we use separate monitors for read versus write operations? In theory, yes. We had that in 8.0.x but it created a lot of complexity around error handling since you never know what the other thread might be doing. Maybe there is a cleaner way

Re: HTTP/2 optimizations and edge cases

Rémy and Mark, On 6/3/16 10:11 AM, Mark Thomas wrote: > On 03/06/2016 14:36, Rémy Maucherat wrote: >> Hi, >> >> With direct connect having been hacked in (err, I mean, "implemented"), it >> is (a lot) easier to do meaningful performance tests. h2load is a drop in >> replacement of ab that uses

Re: HTTP/2 optimizations and edge cases

On 03/06/2016 15:59, Rémy Maucherat wrote: > 2016-06-03 16:11 GMT+02:00 Mark Thomas : > >> On 03/06/2016 14:36, Rémy Maucherat wrote: >>> Hi, >>> >>> With direct connect having been hacked in (err, I mean, "implemented"), >> it >>> is (a lot) easier to do meaningful performance

Re: HTTP/2 optimizations and edge cases

2016-06-03 16:11 GMT+02:00 Mark Thomas : > On 03/06/2016 14:36, Rémy Maucherat wrote: > > Hi, > > > > With direct connect having been hacked in (err, I mean, "implemented"), > it > > is (a lot) easier to do meaningful performance tests. h2load is a drop in > > replacement of ab

Re: HTTP/2 optimizations and edge cases

On 03/06/2016 14:36, Rémy Maucherat wrote: > Hi, > > With direct connect having been hacked in (err, I mean, "implemented"), it > is (a lot) easier to do meaningful performance tests. h2load is a drop in > replacement of ab that uses HTTP/2, and it allowed doing some easy > profiling. > > The

HTTP/2 optimizations and edge cases

Hi, With direct connect having been hacked in (err, I mean, "implemented"), it is (a lot) easier to do meaningful performance tests. h2load is a drop in replacement of ab that uses HTTP/2, and it allowed doing some easy profiling. The good news is that the code seems to be well optimized already