Can you post the ordering of the files? The timeline screenshot didn't give much info. Again, to clarify, the html files are actually arriving later? On Feb 16, 2016 6:18 PM, "Darin Hensley" <[email protected]> wrote:
> Yes, I mean the time per a individual file is much shorter with http2 > push. I had this both on an Amazon and Rackspace server...one Ubuntu and > one Gentoo.... and had the same user experience. The set up is pretty > simple, so I don't think I was doing anything wrong...nothing pointed out > in the github issue I filed for nghttpx. Not sure where the problem would > be. I liked be able to brag I was using http2 push and not having to worry > about concatenation, but happy enough without it. > > > > > > On Tuesday, February 16, 2016 at 12:57:47 PM UTC-6, Justin Fagnani wrote: >> >> I'm trying to follow along here, but I'm having some trouble seeing >> what's happening. The timeline images you have don't show the .html files, >> so I can't see when they're downloaded. When you say "The individual >> time on the files requested are much shorter" do you only mean that the >> time per file is shorter, or do you also mean that the timeline is showing >> that they're downloaded earlier? >> >> I'm particularly interested in the case where the files are downloaded >> earlier with http2 push, but DOMContentLoaded is still firing later. That >> would indicate that something is going wrong in the browser that delays the >> ready/load events. The other case, where the files download quicker, but >> later in the timeline, would line up with the diagnosis that this is a >> server-related issue, or priority+push support in the browser. >> >> Cheers, >> Justin >> >> >> On Mon, Feb 15, 2016 at 10:07 AM, Eric Bidelman <[email protected]> wrote: >> >>> AFAIK, App engine's h2 push doesn't push based on priority. It pushes >>> all resources at high priority. I'm not sure Chrome even supports resource >>> prioritization (yet) for h2 push. But this could definite be a source of >>> your issue if your sure env is pushing html files at a lower priority. >>> >>> One thing you could do is still vulcanize, and vulcanize with crisper. >>> Then h2 push the .js file separately from the rest of the .html. >>> >>> On Sun, Feb 14, 2016 at 5:11 PM Darin Hensley <[email protected]> >>> wrote: >>> >>>> >>>> Not at the moment....but curious, ya'll did your http2 push testing >>>> with Google App engine, correct? I don't have a google cloud(using the >>>> Amazon free for a year cloud) and so I use nginx with nghttpx. I asked the >>>> author and he mentioned it could be that html files get the lowest >>>> prioritization in http2 push. >>>> >>>> Here is the thread for more information: >>>> >>>> https://github.com/tatsuhiro-t/nghttp2/issues/501 >>>> >>>> Can I please get your opinion/input on it? I'm basically resorting back >>>> to vulcanize and not pushing the html files. >>>> >>>> >>>> On Sunday, February 7, 2016 at 7:25:02 PM UTC-6, [email protected] >>>> wrote: >>>>> >>>>> Huh, that's unexpected, and I haven't seen that in our tests. Do you >>>>> have a demo deployed anywhere that we can test with? >>>> >>>> Follow Polymer on Google+: plus.google.com/107187849809354688692 >>>> --- >>>> You received this message because you are subscribed to the Google >>>> Groups "Polymer" group. >>>> To unsubscribe from this group and stop receiving emails from it, send >>>> an email to [email protected]. >>>> To view this discussion on the web visit >>>> https://groups.google.com/d/msgid/polymer-dev/3ce650e5-52f7-4ee7-8e18-67925ea41bd0%40googlegroups.com >>>> <https://groups.google.com/d/msgid/polymer-dev/3ce650e5-52f7-4ee7-8e18-67925ea41bd0%40googlegroups.com?utm_medium=email&utm_source=footer> >>>> . >>>> For more options, visit https://groups.google.com/d/optout. >>>> >>> Follow Polymer on Google+: plus.google.com/107187849809354688692 >>> --- >>> You received this message because you are subscribed to the Google >>> Groups "Polymer" group. >>> To unsubscribe from this group and stop receiving emails from it, send >>> an email to [email protected]. >>> To view this discussion on the web visit >>> https://groups.google.com/d/msgid/polymer-dev/CACGqRCCcsoTUC-TE%3DtoHVMod13uFbOSj67T-MGD7%2BDH8nU9DAQ%40mail.gmail.com >>> <https://groups.google.com/d/msgid/polymer-dev/CACGqRCCcsoTUC-TE%3DtoHVMod13uFbOSj67T-MGD7%2BDH8nU9DAQ%40mail.gmail.com?utm_medium=email&utm_source=footer> >>> . >>> >>> For more options, visit https://groups.google.com/d/optout. >>> >> >> Follow Polymer on Google+: plus.google.com/107187849809354688692 > --- > You received this message because you are subscribed to the Google Groups > "Polymer" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/polymer-dev/e849778d-3e94-4f53-97ed-5149236b15f4%40googlegroups.com > <https://groups.google.com/d/msgid/polymer-dev/e849778d-3e94-4f53-97ed-5149236b15f4%40googlegroups.com?utm_medium=email&utm_source=footer> > . > For more options, visit https://groups.google.com/d/optout. > Follow Polymer on Google+: plus.google.com/107187849809354688692 --- You received this message because you are subscribed to the Google Groups "Polymer" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/polymer-dev/CAEKsHmCMydS4Ms%2BMzZ0pn%3DfFuSU%3DT%2B-tZqUEdBBkzYozCt5jAQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
