MYNITOR.COM

If you are working with your home networking gear, then you must use such integrated device that does it all. You may have 1 box that is a router, firewall, and switch on a home network all in one. Really it’s quite interesting that all the function can fit into one box. Now, there is a quicker and simpler way to get more performance and value out of your network. A router is a hardware device works at layer 3 of the network layer. These days, most of the routers are verifying the source and destination IP address of each packet and route that packet on its way. In case, you are been used to working with the home networking gear that you are used to integrated device “does it all”. On the home network, you might have a box, which is the cable or DSL modem, firewall, router, wireless access point and switch, in one. Also, it is very amazing all functions they will fit in a box today.

In case, you study the Cisco networking & learning about how the businesses make use of the devices, you are thinking wondering why there is a lot of importance on differences between the switch, firewall, router, as well as other devices. In case, home user will have all the devices combined in one, why does not business user do as well? The article can try to answer this question as well as cover differences between the devices.

Integrated devices

Like home devices, and business devices have now become more consolidated with time however not to an extent that home devices have. The network administrators in the business network are comfortable to have the separate devices and like an idea. It is because the network administrators love to isolate the problems down to the certain device as well as they love to know performance abilities of each device. In case, you make use of the integrated router, firewall and switch, all in a device, troubleshooting, understanding and managing, performance capabilities of this device gets very complicated.

If you are looking for easy access and high performance web server, then the Linux based Apache web server is right for you.  It is also faster and reliable than the Windows NT and UNIX based server.  Only the users are required some easy cords to operate it.  You can also remind that all the files required httpd before search in the Apache web server.  However, it is never so critical to access like the Windows NT and UNIX due to easy features.   In case of new web master, it is always better to access the Apache web server of the Linux system as per instruction.

Enable compression of the HTML just by putting in php.ini:

output_handler = ob_gzhandler

In case, you think about that, then it may take you around 0.1 seconds for generating 40K of the HTML in PHP page. But it most likely takes around 6 seconds for user to download page by using the 56k modem without any compresson. With the compression, download can probably take around 2 to 3 seconds. Thus, time taken for the page generation is miniscule when compared to transit time of HTML from server to browser. Thus, biggest speedup you may perform for the modem users is making use of ob_gzhandler! The feature is just recommended for the PHP 4.1.0 and later.

The point was been moved closer to top of list on 9July 2002 while experienced personally benefits of the compression. The PHP scripts are been recompiled each time till scripts are cached. Install the PHP caching product (and I suggest Turck MMCache) to generally increase the performance by around 25 to 100% just by removing the compile times. Switch from the file based sessions to the shared memory sessions. You can compile the PHP with –with-mm choice as well as set session.save_handler=mm in the php.ini. The informal benchmarks suggest session management time is been halved by simple change.

Now, the use of Apache web server of Linux system is high on demand due to its excellent performance and access.  It is also loaded with attractive features that the webmaster can easily access according to the instruction. Like Linux OS system, Apache web server is also easy to access due to simple menus.  It is also never so critical like the Windows NT and UNIX types web server. So, the users are never required more expertise to access it.  It is also required some easy cords that the users can use at the time of operating to boost the server performance.

This can speed up the PHP code by around 5 to 15% in case, you print or else echo in the code. Note output buffering is enabled in case, you are making use of above ob_gzhandler hint. ASP does in IIS. On Windows, the FastCGI is highest performance way to run PHP with the Apache. Though PHP4 will run in the threaded environment, few global locks prevent that from making complete use of the threads. As well PHP is not stable in the threaded environments as a lot of common extensions aren’t thread safe.  In PHP4, the objects & arrays must get passed in & out of the functions by reference and everything by value. In the PHP5, objects are passed automatically by the reference. Example following gives good performance:

function &test(&$obj_or_array)

{

return $obj_or_array;

}

$var =& test($obj);

Be miserly & sparse with the server as well as web pages. Do not run XWindows on server as well as other unneeded processes. The Apache Today has guide on how you can remove them. Also, added 1 Dec 2001 and this hint must just get used for the PHP 4.2.0 as well as above there were the bugs before this. The alternative caching method while you have the pages that do not change very frequently is cache HTML output of the PHP pages and try Smarty or else Cache Lite. Make use of  output buffering.

Today, Apache has considered as leading web server! It has designed to offer a balance of flexibility, performance, and portability. This web server is offering high performance in critical situations. It can enhance the tuning of web site, and prominently enhance appearance of a web site. Have any confusion about the Apache web server; you have the option to investigate about this web server. You can also ask the previous users of Apache to known the function of this server. In this regard, you can get true answer that Apache is the best web server is not. It’s time to use the Apache web server on your website.

Discusses a few sophisticated methods that includes DNS load balancing & mod_backhand. HP/Compaq Apache tune guide in the PDF and complete & includes the benchmarks. After xenu.net was been slash dotted, they published the Apache optimization tips. I realised all above tips deal in squeezing maximum performance from the single server. Finally, in case, you are very successful, tips will not be enough. You will then have to switch to making use of multiple Apache servers (server farm) with load-balancing, clustering, as well as caching. Making use of Squid as the proxy cache and configuring Squid. Rasmus Lerdorf suggests squidGuard.

Deprecated is recommendation to make use of Apache 2 with the threaded PHP SAPI. PHP has a few global locks, which prevent tat from maximizing the concurrency with some multiple threads. Several of Web servers supported to use with the Siebel Business Applications are totally based on Apache Web Server. It includes IBM HTTP Server, Oracle HTTP Server as well as HP Apache Web Server that are been supported on some UNIX & Linux operating systems. Topic describes suggested parameter settings, which are been optimized for the scalability & performance on the Apache Web Server. You may further adjust the settings at the discretion to optimize performance of the Web server.

Apache web server of the Linux is highly scalable creation that able to handle open platform to secure so many pages within few time. It is also offering a save and secure environment to the host server.  The users can get huge number of server package by choosing the Apache web server of the Linux system. It is also a right option for the web developer to get good atmosphere for the webhosting.  Now, you can get more information about the Apache web server of the Linux system as well as their related elements from the website of the Linux software sites.

Default setting for the ThreadLimit for Apache Web Server is of 64, however parameter is set to the higher number, and subject to the limitations from the kernel settings. Associated parameters include MaxClients ThreadsPerChild, as well as ServerLimit. Lots of parameter settings are all subject to accessible memory & other resources. The high values for the parameters like MaxClients and ThreadLimit will increase the memory usage and user lower the values for reducing the memory usage.

* ThreadLimit = 20000 is maximum value that is supported by Apache Web Server and you may set parameter to number the system supports.

NOTE:  ThreadLimit parameter should be executed before parameters.

* ThreadsPerChild = Number of threads every child and cannot exceed the ThreadLimit.

* MaxClients = The maximum connection and can’t exceed ThreadsPerChild.

* ServerLimit = Generally, set the parameter to value of the MaxClients that was divided by value of the ThreadsPerChild. (In case, MaxClients & ThreadsPerChild are set same, set ServerLimit. Most important feature of the web server performance is an amount of accessible RAM.  For the Web server support details, Siebel System Requirements & Supported Platforms on the Oracle Technology. For information to tune Web server, see:

* Specifying Static File Caching

* Applicable server tuning topics for the specific operating systems

* Tuning Siebel Web Extension for UNIX & Linux Platforms

There are many types of web server available but the Apache web server of the Linux is going high on demand. For the operation the users are not required more skilled as well as expertise like other web server. Apache web server is not only cheap with comparison to other but also easy to access. All the software of Linux for the Apache web server is available in the RPM formats. It is also easy for installation and easy for access. However, the users are requires to consider about it that Apache RPM’s filename is stated with the httpd for searching.

Performance Issues with the HostnameLookups & DNS Lookups

It means when you set up the server it is very important to prevent server from making use of swap file since this can dramatically slow down this server. Watch MaxClients setting as webserver might spawn a lot of children that server begins swapping, again the major problem.  MaxClients directive sets limit of the simultaneous requests, which is served.  In case, there are the requests past Maxclients they are queued according to ListenBacklog directive.  Maximum number of the child processes is of 256 for the non-threaded server. Check average Apache process just by opening up top & then divide the size in available memory.  Obviously it is very important to leave extra.

Here is the example of process and note that the top shows the PIDs as the 1383 for apache.  The process is making use of 12,200KB of the virtual memory.  Thus, to follow formula you will take total available memory as well as divide by 1024KB and about 12MB.  That will give you with number of the MaxClients you can add.  However, you can see in the example this server is making use of all the memory thus it will be not wise to add the MaxClients number.

Apache web server of the Linux is in pick because it is making the entire data processing of website easier and faster. There is also some helping software of the Linux available that helps the users to makes entire organize smoother and faster.   In case of other web server various types of web software available in the different formats. So, the users can require changing their entire system setting for installation. However, the Linux based software like the RedHat and Fedora are available in the RPM format that matches to every system setting. However, the users are requires to consider when the Apache RPM’s filename will start from the httpd.

Making use of HostnameLookups needs DNS lookup before request is done adding the considerable latency.  Thus, HostnameLookups must get turned off.   In case, you are making use of Allow and Deny from the domain directives you may make the double reverse DNS lookups as first is the forward lookup as well as second is the reverse lookup and verify it’s not spoofed.  It means that you must make use of IP Addresses to make Allow & Deny directives. It is likely to limit the DNS lookups to one feature of Apache server process, example limiting the DNS lookups just for the html and cgi processes.  Here is the example:

HostnameLookups off

<Files ~ “\.(html|cgi)$”>

HostnameLookups on

</Files>

In case, you make use of Allow from the domain or else Deny from the domain, it an increase latency since you may need Apache to do the DNS lookup for every domain setting.  It is good to use the IP Address in this situation.

Use Specific DirectoryIndex

Avoid situation where server needs to figure wildcard option for DirectoryIndex.  Instead of making use of wildcard setting just like this:

DirectoryIndex index

Use specific setting:

DirectoryIndex index.html index.cgi index.pl

You save small amount of the resources just by having most used choice first in list.

Apache is an excellent and reputed Linux-based Web server. It is know use in place of other expensive server’s designs due to faster processing and performance. It is also simple for installation. Once the users can setup the DNS correctly, then they can access the internet easily. Also, the users need to organize Apache that accepts the surfers stand to access their website. So, it is more essential for the users to know the process of configure Apache because it is more required for the success of this process. For easy access the Linux has also offered much software that is making the process easier and faster. In order, to tune very well, you have to benchmark the Web server. You may get a few benchmark figures by using the ApacheBench or httperf. In case, you are the OS agnostic, I suggest making use of Microsoft’s excellent Web Application Tool.

WAST is flexible than ab as it allows you define various GET parameters for every thread. It is very important as it allows you simulate the multiple PHP sessions through PHPSESSID GET parameter. You need to avoid benchmarks that involves PHP sessions while using the ab as sessions can become the artificial bottleneck. More information  on making use of WAST with the PHP. In order, to monitor Apache server, I make use of command top d 1 that displays CPU & memory usage of processes on machine as well as apachectl status.

General rule of the thumb for the hardware upgrades: For the PHP scripts, main bottleneck is CPU. For the static HTML or images, bottleneck is RAM & network. According to the Compaq benchmarks at 1999 (original article is lost because of bitrot), slow 400 Mhz Pentium will saturate the T3 line (that is 45 Mbps) with the static HTML pages. The PHP script is served 2 to 10 times slower than the static HTML page by the Apache. Try and use more of the static HTML webpages as well as fewer scripts.

Well, there are many Linux users are wondering for the best web server for the improvement in their system. In this regard the nginx web server is offering them the best possible result. It is becoming a very popular web server due to its reliability and flexibility. Its configuration is well documented and best for some body that is just new to the web server. If you are new to the web server then it’s the nginx web server is just the right option for you. This web server is available in default packages on many Linux systems. It is an open source soft ware program and any one can modify it according to their requirements. Continuing along low memory meme – I also have done lots of testing with the Apache with time, what I have actually found is Apache scales well, providing memory allows – and it goes splat. In some other words, making the Apache work in greater load, you have got 2  choices:

1. Decrease Apaches memory footprint (and you may get that quite small)

2. Add memory

Ostensibly, number of the concurrent requests Apache will handle is:

Anyway, with the 256MB VPS – you do not even wish to go there. Doesn’t matter how much you can optimise, you end up with the built in the scalability limit. Thus, I took close look at the Lighttpd & Nginx.

Web Servers –New Breed

These 2 web servers generally come from different backgrounds, still are rather similar. And both are called – asynchronous servers, when opposed to request every process model of the Apache. Lighttpd is the single threaded server that was developed famously to solve C10K problem; this is, to serve around 10,000 simultaneous links. NginX originates from Russia; and was written for the rambler.ru that is Russias busiest site. That runs with the single master procedure that delegates the work to small number of the worker processes; thus not very single threaded –however light footed, we may say.

If you are searching for one of the most popular web server for your Linux system, then it’s the lighttpd web server can really help you. Almost higher percent of users are using this web server for its best flexibility, stability and reliability. The configuration of lighttpd web server is very easy and simple to perform just like the Apache web server. Most of the web server administrators choose this web server over others due to various functionalities. It has proven itself in the long run and you don’t need to mistrust its capabilities. By using lighttpd web server in your Linux system now the user can get various flexibilities in their operation.

Actually, I did not know there was something beyond Apache till recently, while I read this You Tube make use of Lighttpd to serve more than 100million crap videos, daily! As anybody who follows the blog may know, I am using Django for developing the new web application (I’m liking that a lot). Django is the Python, and using Python on the Apache you are been supposed to make use of mod_python. mod_python is the excellent piece of the software, it is very quick– and exposes Apaches API. Thus, anything you may do by writing the Apache module in c, and you may do in the mod-python making use of python – and it is very bloody fast.

Drawback is memory; and mod-python has the bad rep for the memory (though in case, you read the Grahams comments on the post, you can see that there are 2 sides of the story). Regardless, Apache is the multithreaded beast –as well as under moderate load you may start to need memory. I am building the web application for operating in the memory confined VPS, thus, even with the optimisations mod_python at Apache actually is not perfect for me. Fortunately, Django can as well run fastcgi, and when I have not done serious load testing– early indications are it appears very reliable.