icing.github.io/mod_h2/nimble.html
> Please have a look. Anything you'd like to add or changed, just make a PR!
>
> Thanks for the investigations and data!
>
> Cheers,
>
> Stefan
>
>> Am 21.01.2017 um 11:50 schrieb Stefan Eissing :
>>
>>
>>&g
* ... and by "here" I meant "here
<https://docs.google.com/document/d/1KZyWfaLrXVvwG6REjJ_TT0KiV1u1rTLsedgN74oCGTw/edit?usp=sharing>
"
On Thu, Jan 19, 2017 at 6:54 PM, Kyriakos Zarifis
wrote:
> Sounds great!
>
>
>> Very interested. I'd like to
Sounds great!
> Very interested. I'd like to add a page over at
> https://icing.github.io/mod_h2/ about it, so that people can easily grasp
> what the advantages are. For that, your numbers (do you have screenshots of
> browser timelines maybe?) would be very welcome. Also that someone besides
>
, Stefan Eissing <
stefan.eiss...@greenbytes.de> wrote:
> Hi Kyriakos,
>
> maybe you can give https://github.com/icing/mod_h2/releases/tag/v1.8.8 a
> try in your setup? I would be interested if it gets rid of the 100ms delay
> in response processing. Thanks!
>
> Cheers,
>
&g
s much more nicely for you. You find it at
> https://github.com/icing/mod_h2/releases/tag/v1.8.7
>
> Thanks,
>
> Stefan
>
> > Am 02.01.2017 um 23:33 schrieb Kyriakos Zarifis :
> >
> > Thanks Stefan!
> >
> > I just tried the tweaked version. I thi
ore (another word
> for agile, pls) to stream changes. Please let me know if that had any
> effect on your tests.
>
> Thanks,
>
> Stefan
>
> > Am 29.12.2016 um 12:40 schrieb Kyriakos Zarifis :
> >
> > That means the images should get a minim of ~30% of th
>
> That means the images should get a minim of ~30% of the available
> bandwidth as long as they have data. My reading.
Right. Makes sense.
> 1. priority dependencies: streams with lower prio, but depending on a high
> level stream, inherit this priority. This would make all preloads
> *together* have the same prio as page B. Last I knew, chrome did no
> dependencies. Were these resources PUSHed by the server?
>
Not PUSHed; they were
I am experimenting with contention between lower/higher priority HTTP/2
streams, and I think I am noticing that high-priority frames are not given
high priority (quickly enough)
The process is: Download dummy page A, which, after onLoad, Prefetches 8
objects (5MB each) at low priority. While the
Hi,
TL;DR:
I've been experimenting with HTTP/2 Push and Prefetch to preposition
content on the client before it requests it, and specifically I want to
evaluate the pitfalls of prepositioning objects aggressively, with regards
to how it could impact the delivery of higher priority objects.
While
10 matches
Mail list logo
