PUBLIC MARKS from camel with tags linux & performance

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

User contributed tutorial written by Ramesh Natarajan. Following are few situations where you may be interested in performing a filesystem benchmarking. => Deploying a new application that is very read and write intensive. => Purchased a new storage system and would like to measure the performance. => Changing the RAID level and would like to measure the performance of the new RAID. => Changing the storage parameters and would like to know the performance impact of this change

Iperf est un des outils indispensable pout tout administrateur réseau qui se respecte. En effet, ce logiciel de mesure de performance réseau, diponible sur de nombreuses plateformes (Linux, BSD, Mac, Windows…), se présente sous la forme d’une ligne de commande à executer sur deux machines disposées aux extrémités du réseau à tester.

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.