Polaris system loads Web pages 34% faster

Amazon, for example, estimates that every 100-millisecond delay cuts its profits by 1 percent.
Click to expand...
:wtf:
 
Polaris needs to be installed on the server, and includes a tool — called Scout — that loads pages locally and extracts all the various dependencies in order to create the dependency graph that Polaris then uses to optimize how webpages are loaded.

“By the time the client request arrives at the server this graph is already computed. Generating the graph is not user triggered,” Netravali notes, although he also confirms that if substantial changes are made to a website then the mapping process would need to be re-run for the load time acceleration to be maintained.
Click to expand...

http://techcrunch.com/2016/03/09/mit-develops-a-new-technique-to-load-webpages-faster/
 
Isn't it similar to this ?

http://community.brocade.com/t5/vAD...n-for-Stingray-Traffic-Manager-9-5/ta-p/73684

Minification removes unnecessary characters from JavaScript and CSS files, including whitespace (space, newline, tab) and developer comments. This significantly reduces the size of these files, resulting in a reduction in bandwidth usage and download time

Aptimizer Express includes image data in CSS files by encoding the data as Base64 and using a data URI to insert it in the style sheet. Including the image data in the style sheet eliminates a request/response roundtrip between the browser and server, which ultimately speeds up page load times

Many websites download images that are higher quality than actually required. Aptimizer Express resamples JPEG images, which reduces the file size without any perceivable visual difference when compared to the original image

Aptimizer Express automatically strips redundant metadata information from images resulting in smaller file sizes and reduced bandwidth usage. This data can include exif, date/time, and descriptive information.

etc etc
 
Another band aid for an ancient technology that should just die...

HTTP 1.1 is the problem, because it needs to establish an entire new connection for each resource that needs to be fetched by the browser. Its also a text only protocol, and that introduces overhead and encoding schemes that can grow your transferred data cost by 30%.

HTTP 2 standardized last year already and all of the big browsers support it. It pipes requests in a single connection, and can enforce proper compression over that single pipe,unlike HTTP 1.1 that can only do it per file served.

Optimizing will help for now, and the technology is interesting, but if they want to see real results, they'll need to switch to something better.
 
NeoAcheron said:
Another band aid for an ancient technology that should just die...

HTTP 1.1 is the problem, because it needs to establish an entire new connection for each resource that needs to be fetched by the browser. Its also a text only protocol, and that introduces overhead and encoding schemes that can grow your transferred data cost by 30%.

HTTP 2 standardized last year already and all of the big browsers support it. It pipes requests in a single connection, and can enforce proper compression over that single pipe,unlike HTTP 1.1 that can only do it per file served.

Optimizing will help for now, and the technology is interesting, but if they want to see real results, they'll need to switch to something better.
Click to expand...

How can I start utilizing http 2?
Sorry if this is a dumb question. Will this require me to modify apache?

Also how does this compare to google's SPDY?
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X