Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
igrigorik
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
9 ms
·
61.
▲
Uplink Latency of WiFi and 4G Networks
(igvita.com)
4 points
by
igrigorik
12y ago
|
0 comments
62.
▲
Why is my CDN 'slow' for mobile clients?
(igvita.com)
4 points
by
igrigorik
13y ago
|
0 comments
63.
▲
by
igrigorik
13y ago
This behavior is not defined by the spec / left to the UA. At the moment, I don't believe either WebKit or Blink implementation will swap the image on (desktop) zoom.
64.
▲
by
igrigorik
13y ago
They're complementary. <picture> uses subset of original srcset spec to meet the "resolution switching" use case - e.g. see Example 1 [1]. If you want to select an asset based on viewport width, then you'd either u
65.
▲
Is TLS Fast Yet?
(istlsfastyet.com)
5 points
by
igrigorik
13y ago
|
0 comments
66.
▲
by
igrigorik
13y ago
As far as the browser is concerned, there is no distinction between icon fonts or any other fonts. If your icon font fails to load within 3s then it'll go ahead and try to paint the page with a fallback -- the results of that will vary
67.
▲
by
igrigorik
13y ago
We instrumented Chrome and measured the download times: approximately ~1.1% of font loads are longer than 3s. New timeout will help address that 1.1% by using a system fallback. http://www.igvita.com/2014/01/31
68.
▲
Optimizing Web Font Rendering Performance
(igvita.com)
3 points
by
igrigorik
13y ago
|
0 comments
69.
▲
by
igrigorik
13y ago
I don't know the details of your benchmark methodology or setup (server / client), so not sure I can offer a meaningful response... short of: let's not confuse "my benchmark failed" with "the future doesn'
70.
▲
by
igrigorik
13y ago
Seems coincidental. Just highlights that we need HTTP/2, and the sooner the better... Inventing your own app-layer multiplexing on top of HTTP (via base64 chunks - ugh), is not an interesting problem to be solving in 2014.
71.
▲
by
igrigorik
13y ago
We have a lot to learn on how to use server push effectively. That said, let's analyze some actual use case.. a) Page A currently inlines half dozen small assets on every page. These inlined resources inflate every page and are deliver
72.
▲
by
igrigorik
13y ago
Short answer, yes. Longer answer, there are two ways QUIC can succeed: a) QUIC makes headway on its own, delivers significant perf win, moves to IETF and becomes a standalone protocol in the long run. b) TCP and TLS leverage techniques &
73.
▲
by
igrigorik
13y ago
Some recent SPDYv3 vs HTTPS performance numbers from various Google properties: http://blog.chromium.org/2013/11/making-web-faster-with-spdy...
74.
▲
by
igrigorik
13y ago
Wohoo! https://twitter.com/jnunemaker/status/420634885552754688 :)
75.
▲
by
igrigorik
13y ago
You guys are awesome. Kudos!
76.
▲
by
igrigorik
13y ago
If by ouch, you mean AWESOME . Then I'm totally with you! Wohoo!
77.
▲
by
igrigorik
13y ago
No need to buy anything, it's an MIT-licensed project, and a trivial implementation under the hood to boot. If I wasn't learning Go while writing it, I think it would take all of 5-10 minutes to replicate (including deploying to p
78.
▲
by
igrigorik
13y ago
Yup, that's a great tip. For those not familiar with OSCP stapling: http://chimera.labs.oreilly.com/books/1230000000545/ch04.htm...
79.
▲
Optimizing Nginx TLS Time To First Byte
(igvita.com)
131 points
by
igrigorik
13y ago
|
12 comments
80.
▲
Making the Web Faster with HTTP 2.0
(queue.acm.org)
5 points
by
igrigorik
13y ago
|
0 comments
81.
▲
Configuring and Optimizing WebSocket Compression
(igvita.com)
16 points
by
igrigorik
13y ago
|
2 comments
82.
▲
by
igrigorik
13y ago
Doh! On it.. In the meantime, this is the link you want: https://developers.google.com/chrome-developer-tools/docs/re...
83.
▲
Please update old and buggy F5/BIG-IP firmware
(imperialviolet.org)
5 points
by
igrigorik
13y ago
|
0 comments
84.
▲
The Performance of Open Source Applications
(aosabook.org)
1 points
by
igrigorik
13y ago
|
0 comments
85.
▲
Retrospective: High Performance Browser Networking
(igvita.com)
9 points
by
igrigorik
13y ago
|
0 comments
86.
▲
Pure ruby implementation of HTTP 2.0 protocol
(github.com)
1 points
by
igrigorik
13y ago
|
0 comments
87.
▲
by
igrigorik
13y ago
I think there is something else going on here. While it's plausible that different browsers may introduce some processing latency, we are definitely not talking about 100ms+ delays, or 30 to 8Mbit throughput drop. More likely.. try dis
88.
▲
by
igrigorik
13y ago
AFAIK, no.. Maybe in private. If you're interested, checkout the Chromium source, there is a basic demo server checked in. Perhaps more importantly, we don't encourage people to at this point because it's a fast moving target
89.
▲
by
igrigorik
13y ago
That's not a joke - it's true... The joke part of it is in: there are two types of systems at Google, the ones that are deprecated, and the ones that are not yet ready for production.
90.
▲
Automating DPR switching with Client-Hints
(igvita.com)
4 points
by
igrigorik
13y ago
|
0 comments
More ›