Recommended Posts

615411275.png

Left is SPDY enabled, right is with it disabled.

The onload times are skewed a but, due to things Google loads in, but is you look at the graphs you can see that objects hosted on the same IP take less time to load, and spend less time waiting (Classical HTTP uses 1 connection per resource, SPDY uses 1 connection per IP for all resources, and stuff like WebSockets)

Edit: The cyan in the graphs is "time spent waiting to connect", SPDY doesn't suffer from that since it multiplexes data into the single connection, allowing other resources to load without having to wait.

Edit 2: I was wrong :laugh: Cyan is DNS lookup, the green is connecting. That said, I think either Firebug is mishandling the values, or Firefox is reporting stuff wrong, as the times can be a bit strange (0ms to transfer 10KB of content, but 500ms to transfer 15KB?)

Strange, problem exist, so looks like there is some other dependence, since now I start think about SPDY enabled in my build....

The only time I crash is if I enter About:Memory into the URL Bar. A Bug report has been filed:

Bug 708248 - Crash in mozilla::storage::StorageSQLiteMultiReporter::CollectReports with Stylish 1.2.4 enabled

Yeah, I had stylish running. I only have one script for it so I disabled it for the time being until they get the recent bugs straightened out. Seems like they added quite a bit of code this week. Otherwise, there is still Aurora to fall back on until the dust clears.

Also previously it was decided that if Silent Updates (Removal of UAC dialog and update progress bar) land early development phase of FF then these will be also land in Aurora FF10, now they missed the train, it maybe now only in FF11 and FF12.

Also addons default to compatible dream..

You was right, in today's build it is out...shame.

https://bugzilla.mozilla.org/show_bug.cgi?id=709193 looks like this is big problem....

Yeah, it's the second time they're run into this issue. One problem is that they compile 32bit builds on 32bit systems, so at most they're limited to 3GB of RAM for the compile tools (which they're now using), moving to 64bit systems for the 32bit builds will give them 4GB of RAM, which they'll also hit soon enough.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now