PUBLIC MARKS from camel with tags http & 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.

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

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.