Today it has been announced that if you are using the Wheezy image of Raspbian you can update to allow dynamic overclocking without voiding warranty. I’ve been using my Raspberry Pi for a little while now and have begun to notice the CPU limitations when compiling code and performing other tasks so I jumped at the opportunity to give this a go. I’ll briefly go through the steps I went through in order to update the OS, as well as provide a basic benchmark that will display the changes.
Monthly Archives: September 2012
The purpose of Cloud Linux is to improve the overall stability, reliability and performance of a shared server. Cloud Linux limits each individual account to a set amount of CPU and memory (RAM) resources. This means that rather than a server going under load and becoming slow for all users on it, only the account causing problems will be restricted. As Cloud Linux is becoming more common on shared hosting servers, it is important to know how to troubleshoot common problems that come up when using it to get the most out of your website and hosting environment.
I’ve used Cloud Linux for over a year now and think it’s great when used correctly, this article includes everything I have learned while using it during that time. A lot of users don’t like it because they have experienced it cutting the performance of their websites. With this guide you will be able to pin point issues and then work on resolving them. Although this information is aimed towards the server administrator, users within the Cloud Linux environment will find useful information for checking logs to find problems with their websites.
This article will be focused around cPanel, however most of the main points about Cloud Linux will still be directly useful for other control panels, such as Plesk.
I’ve been benchmarking different web servers recently and this post contains all of my results as well as information on how the tests were performed during the process.
I have benchmarked Apache 2.2, Apache 2.4, Nginx, Lighttpd, Varnish, Litespeed, Cherokee and G-WAN web servers when running on 1 CPU core, 2 CPU cores, 4 CPU cores and 8 CPU cores while loading a 100 byte static HTML page to determine the difference between them in performance.