PUBLIC MARKS from camel with tags web & performance

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.

Pagetest is an open source tool for measuring and analyzing web page performance right from your web browser. AOL developed Pagetest internally to automate load time measurement of its many websites, and it has evolved into a powerful tool for web developers and software engineers in testing their web pages and getting instant feedback. We decided to release it to the grander web development community to further help evolve it into an even more useful - and free - web performance tool.

PageTest allows you to provide the URL of a webpage to be tested. The test will be conducted from the location specified and you will be provided a waterfall of your page load performance as well as a comparison against an optimization checklist.

Improving performance starts with metrics. How long does it take for the page to load? Seems like a simple question to answer, but gathering accurate measurements can be a challenge. In my experience, performance metrics exist at four stages along the development process.

Opsview is enterprise network and application monitoring software designed for scalability, flexibility and ease of use. Opsview has been in development since 2003 and is released under the GNU GPL license. Current version is 2.12. Opsview is a fully integrated monitoring tool that incorporates popular Open Source software including Nagios, Net-SNMP and RRDtool. The Catalyst web framework provides an extensible monitoring and configuration user interface. Opsview software is supported on Linux (Debian, CentOS, RHEL and Ubuntu) and Solaris 10. It will monitor all common operating systems including Windows. Opsview extends the capabilities of Nagios in the following ways: * Distributed monitoring with high availability and fail-over * Much improved SNMP support with trap processing with rules engine * API supporting automation of Opsview configuration * Data warehouse for storage of historical performance and event data * Opsview Reports customisable reporting * Powerful configuration and management UI * Extended monitoring UI * Extensible architecture based on Catalyst Web Framework and Altinity middleware software

Quand on pense à l’optimisation du temps de chargement d’un site, on pense généralement à améliorer le temps de génération des pages sur le serveur web. Hors, ce temps ne représente que 10 à 20% du temps de rendu de la page. Il existe en revanche des techniques directement applicables ayant un réel impact sur les performances. C’est pour expliquer ces différentes techniques que j’ai décidé de participer pour la troisième fois en tant que conférencier aux Intellicore Tech Talks. Comme je l’annonçais il y a quelques jours, j’ai fait cette présentation avec Nicolas Chevallier, ingénieur Polytech’Nice-Sophia, consultant Astek et créateur de Allogarage.fr.

Caching is the temporary storage of frequently accessed data in higher speed media (typically SRAM or RAM) for more efficient retrieval. Web caching stores frequently used objects closer to the client through browser, proxy, or server caches. By storing "fresh" objects closer to your users, you avoid round trips to the origin server, reducing bandwidth consumption, server load, and most importantly, latency. This article shows how to configure your Apache server for more efficient caching to save bandwidth and improve performance. Caching is not just for static sites, even dynamic sites can benefit from caching. Graphics and multimedia typically don't change as frequently as (X)HTML files. Graphics that seldom change like logos, headers, and navigation can be given longer expiration times while resources that change more frequently like XHTML and XML files can be given shorter expiration times. By designing your site with caching in mind, you can target different classes of resources to give them different expiration times with only a few lines of code.

Enquisite produces increasingly granular reports on your website's activity in search engines. Working in conjunction with other web analytic tools, Enquisite provides information and metrics webmasters can't get anywhere else. Easy to read with flexible parameters and mapping, Enquisite search engine metrics give you the edge in the organic and PPC search markets. * = search engine ranking analysis and reports Search Engine Ranking Reports Graphic reporting on search traffic and ranking data down to city and zip/postal code * Know Your Customers' Queries Know Your Customers Keyword and traffic analysis to explain why and how site visitors access your business

This article shows 2 awesome ways to implement caching on your website using Apache .htaccess (httpd.conf) files on the Apache Web Server. Both methods are extremely simple to set up and will dramatically speed up your site!

You can benchmark Apache, IIS and other web server with apache benchmarking tool called ab. Recently I was asked to performance benchmarks for different web servers. It is true that benchmarking a web server is not an easy task. From how to benchmark a web server, “First, benchmarking a web server is not an easy thing. To benchmark a web server the time it will take to give a page is not important: you don’t care if a user can have his page in 0.1 ms or in 0.05 ms as nobody can have such delays on the Internet.

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.

Applications using the LAMP (Linux®, Apache, MySQL, PHP/Perl) architecture are constantly being developed and deployed. But often the server administrator has little control over the application itself because it's written by someone else. This series of three articles discusses many of the server configuration items that can make or break an application's performance. This second article focuses on steps you can take to optimize Apache and PHP. Linux, Apache, MySQL, and PHP (or Perl) form the basis of the LAMP architecture for Web applications. Many open source packages based on LAMP components are available to solve a variety of problems. As the load on an application increases, the bottlenecks in the underlying infrastructure become more apparent in the form of slow response to user requests. The previous article showed you how to tune the Linux system and covered the basics of LAMP and performance measurement. This article focuses on the Web server components, Apache and PHP.

Vitamin Features » Enhance your (page) performance!

Twenty Things You Didn't Know You Could Do with Your Apache Web Server Caching

ONLamp.com -- Caching Dynamic Content with Apache httpd