PUBLIC MARKS with tags configuration & server

MySQLTuner is a script written in Perl that will assist you with your MySQL configuration and make recommendations for increased performance and stability. Within seconds, it will display statistics about your MySQL installation and the areas where it can be improved. It’s key to remember that MySQLTuner is a script which can assist you with your server, but it is not the solution to a badly performing MySQL server. The best performance gains come from a thorough review of the queries sent to the server, and an evaluation of the MySQL server itself. A qualified developer in your application’s programming or scripting language should be able to work with a MySQL database administrator to find improvements for your server. Once the server and application are optimized well, you may need to consider hardware upgrades to the physical server itself. This is a really useful tool for helping to optimize MySQL performance.Understanding the various my.cnf variables and how they affect performance can seem really complicated but this tool takes some of the pain away and makes it easier to understand the effects of each variable.It is especially useful to be able to see the global memory usage, memory usage per thread and the maximum possible memory usage - that is really valuable information that is otherwise complex to calculate.

The configuration described here is not very complicated but still needs to be done carefully. You are expected to have at least basic knowledge of: * MySQL (creating a database, granting access to users, basic SQL queries) * SMTP (what it is and what a basic SMTP dialog looks like) * POP3, IMAP (what they do and what the differences are) * basic Postfix configuration (understand the default settings in your main.cf, have read through the basic configuration document and know that your mail log file is at /var/log/mail.log) * Debian/Linux (general system administration, using a text editor, reading log files)

This article explains how you can install and configure apache2-mpm-peruser on a Debian Etch server. apache2-mpm-peruser is an MPM (Multi-Processing Module) for the Apache 2 web server, very similar to apache2-mpm-itk, but faster (almost as fast as apache2-mpm-prefork). mpm-peruser allows you to run each of your vhosts under a separate UID and GID - in short, the scripts and configuration files for one vhost no longer have to be readable for all the other vhosts. It is based on metuxmpm, a working implementation of the perchild MPM. The result is a sane and secure web server environment for your users, without kludges like PHP's safe_mode.

This TechNote explains what the Request timeout and threadWaitTimeout settings are and how they work. Note: Screenshots are from CFMX 6.1 Administrator but information also applies to CFMX 7.

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.

Enomalism Beta Program ¶ The Enomalism cloud computing platform currently in beta and is available to select Enomaly partners. Please enter tickets using the New Ticket link above. Full source code is available under Browse Source. What is Enomalism? ¶ Enomalism is an open source web-based virtual infrastructure platform. Designed to answer the complexity of managing globally disperse virtual server environments. Enomalism helps to automate the transition to a cloud computing environment by reducing an IT organizations overall workload. The easy to use dashboard can help with issues including deployment planning, load balancing, automatic VM migration, configuration management, and capacity diagnosis.

You are not a Linux expert, Artica for Postfix allows you to install a full solution by one single command line: * Postfix: Main MTA * Kaspersky Anti-spam: powerfull Anti-spam provided by Kaspersky Inc * Kaspersky Anti-Virus * Bogofilter : Bayesian anti-spam * OpenLDAP: Database for main configuration and user management * emailrelay: little SMTP server (used as a content-filter) * SQLite library: zeroconf sql database engine with high perfomances. * Cyrus-imap: powerfull MDA System * Procmail: MDA Filter * Fetchmail: Email retreival * DnsMasq:DNS forwarder and DHCP server * Mailman:Mailing List manager * Sieve: End-user mail filters * Yorel script: Statistics of yorel * QueueGraph: Statistics for postfix * MailGraph: Statistics for postfix * AWSTats and geoip plugin: Statistics set for postfix * renattach: attachments filter

Xen is great. But installing more than one network card became a pain when I tried it the first time. There are some documents describing the principle but I was unable to find a real life example somewhere else. So this is a summary about how it works here now. Using a bridge for a Dom is generally a good idea but then all packets traversing the bridge can be intercepted by any Dom that is using the same bridge. Having a single network card in a Xen landscape also means that theoretically each Dom would be able to sniff all packets traversing this single network card including packets to and from other Doms. A solution is to have more than one network card attached to Xen using a single network card for a single dom. The scenario described here has a server with 3 network cards installed. The first card should be used to access Dom0 and some other DomNs while the second and third network card should be used to purely access Dom1 rsp. Dom2. The Dom configuration file just needs to select the appropriate bridge for each dom.

The Enomalism Virtualized Management Dashboard (VMD) is a powerful web-based virtual server manager. Designed to answer the complexity of managing globally disperse virtual server environments. Enomalism helps to ease the transition to a virtualized environment by reducing an IT organizations overall workload. The easy to use dashboard can help with issues including deployment planning, load balancing, automatic VM migration, configuration management, and capacity diagnosis.

Using NTP is a great way to keep your system clock set correctly. It works by contacting a number of servers around the world, asking them for the time and then calculating what the correct local time is from their responses.

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.

Virtual Iron enables server partitioning for single and multi-server configuration and advanced management capabilities for rapid provisioning, high availability (LiveMigrate™, LiveRecovery™), disaster recovery (LiveRecovery™), workload management and policy-based automation (LiveCapacity™). With these advanced capabilities, users can: