PUBLIC MARKS with tags http & performance

RED is a robot that checks HTTP resources to see how they'll behave, pointing out common problems and suggesting improvements. Although it is not a HTTP conformance tester, it can find a number of HTTP-related issues.

Rules for making your website faster. Reducing the number of HTTP requests is the most important.

"Here are some statistics about the size, number of resources and other such metrics of pages on the world wide web. These are collected from a sample of several billions of pages that are processed as part of Google's crawl and indexing pipeline."

Le concept de ces outils est le même : on prend une URL, on lance la page, et on trace la cascade des requêtes HTTP avec quelques statistiques. C’est là qu’on voit le temps pris par chaque composant, par la somme des composants, et les éventuels problèmes de performance comme les scripts bloquants.

Caching is a great example of the ubiquitous time-space tradeoff in programming. You can save time by using space to store results. Fewer downloads means a faster, happier site.

If you're a frequent visitor to code.google.com for product updates and reference materials for Google APIs you're working with, you might have noticed that the page loading time (or page rendering time depending on how you see it) has reduced in varying

Apache Synapse offers a wide range of connectivity, including HTTP/S, JMS, (S)FTP, SOAP, WS-ReliableMessaging and WS-Security. The project has been designed to allow administrators to support advanced functionality such as load-balancing, throttling, and failover without writing code. The new Apache Synapse 1.1 release includes many enhancements based on feedback from users, including * Apache VFS based file transport - supports File System, FTP, SFTP, JAR, ZIP, TAR, GZIP, Mime * Scheduled Task support makes it simple to run repetitive tasks * XQuery mediator - simplifies XML transformation with the XQuery standard * POJO Command mediator - allows the creation of message-independent mediation logic * DB Report and DB Lookup mediators - support message augmentation and database logging * Cache and Throttle mediators/enhancements - improve performance and manage load on existing services * Split/Clone/Aggregate mediators - support batch processing of large messages * Improved logging and tracing support With asynchronous support for HTTP and HTTPS, Apache Synapse has very high scalability under load, supporting thousands of concurrent connections even with limited threads. Combined with streaming XML support, Apache Synapse has class-leading performance results. The Apache Synapse code and binaries are available from the website at http://ws.apache.org/synapse

CSS Sprite is a single image file which contains several graphics. Using CSS background positions it’s possible to display any one of the graphics. By using a sprite you save on multiple http requests which helps speed up the rendering of your page.

CSS sprites are a way to reduce the number of HTTP requests made for image resources referenced by your site. Images are combined into one larger image at defined X and Y coorindates. Having assigned this generated image to relevant page elements the background-position CSS property can then used to shift the visible area to the required component image.

another way to save precious HTTP hits from your page

Speed up your web pages with YSlow YSlow analyzes web pages and tells you why they're slow based on the rules for high performance web sites. YSlow is a Firefox add-on integrated with the popular Firebug web development tool. YSlow gives you: * Performance report card * HTTP/HTML summary * List of components in the page * Tools including JSLint

Apache server performance can be improved by adding additional hardware resources such as RAM, faster CPU, etc. But most of the time, the same result can be achieved by custom configuration of the server. This article looks into getting maximum performance out of Apache with the existing hardware resources, specifically on Linux systems. Of course, it is assumed that there is enough hardware resources - especially enough RAM that the server isn’t swapping frequently. First two sections look into various Compile-Time and Run-Time configuration options. The Run-Time section assumes that Apache is compiled with prefork MPM. HTTP compression and caching is discussed next. Finally, using separate servers for serving static and dynamic contents is covered. Basic knowledge of compiling and configuring Apache and Linux are assumed.