Current time: 02-28-2021, 11:35 AM Hello There, Guest! (LoginRegister)

Post Reply 
 
Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
A bit confused about chrome results
03-20-2012, 08:28 AM
Post: #6
RE: A bit confused about chrome results
Yeah, I'm not giving up on it yet. Here is what it looks like navigating to http://www.gogle.com first and then going to the page: http://www.webpagetest.org/result/120319...1f5eeae76/ (the penalty is gone).

I'm trying to figure out what bits in Chrome aren't initialized and see what it takes to get them warmed up (assuming it is "fair" and it wouldn't be cheating - like loading the recent apps page).

I can also capture the timeline data from Chrome and record it with the test data to compare to WPT's view of the world to see how they line up (the timeline is from the perspective of the renderer and there are some IPC jumps that could show up differently). In normal operation Chrome starts a new renderer process for each domain so things get pretty muddy looking beyond just the site performance itself (not to mention all of the predictive fetching and lookups that get disabled because I'm using a clean user profile).

Anyway, I'll post here as I try a bunch of different things.

Out of curiosity, how are you measuring first paint in the field? It's not an event that the browsers expose to script - I'm assuming you have a proxy of some kind? It's also worth noting that Chrome had a bug in it's navigation timing implementation where the start time was not including the renderer startup times and was being recorded later than it really should have been (not sure if that impacts your measurements at all).

Thanks,

-Pat
Visit this user's website Find all posts by this user
Quote this message in a reply
Post Reply 


Messages In This Thread
RE: A bit confused about chrome results - pmeenan - 03-20-2012 08:28 AM

Forum Jump:


User(s) browsing this thread: 1 Guest(s)