LiteSpeed is a fantastic product despite its premium cost, it’s worth the extra cash investment.
We owe much of our success at NameHero to our high-speed infrastructure that is optimized for blazing fast performance. This makes our customers’ websites load ridiculously fast when compared to the more traditional hosting packages offered by the “Big Box” competitors around the web hosting industry. Our speed comes partly from the enterprise-grade server hardware that we deploy, but just as important is how we leverage LiteSpeed Web Server in all our servers. If your site is hosted at NameHero, you can bet that it’s running on LiteSpeed rather than the more traditional LAMP Stack solutions which rely on Apache Web Server.
Have you ever needed to know more about working with table size in PostgreSQL? Well this one is for you, check out the excerpt below and head on over to the NameHero Blog to devour this tasty snack.
In this article, we will focus on the topic of table size in the PostgreSQL database environment. We will cover the three major components that make up a table, how to calculate the size of those components as well as the total overall size of a given sample table. When finished, we will have addressed several common questions related to PosgreSQL tables.
Checkout my article on the NameHero.com blog about how to use the TAR command on the Linux command line. It’s a meaty one, I’ve included the opening excerpt and topic links below.
Tar is an immeasurably useful archival tool available on most Linux/Unix-based systems. It is used regularly as part of Linux systems administration at all skill level. This article will tackle a number of common usage case and questions regarding tar. When finished, you will have learned how to effectively utilize tar archives to: compress, create, extract, modify, and otherwise operate on archive files in your day to day workflows. Before we being, lets review the full list of questions this article will answer.
This series is focused on harnessing the power of your Apache configuration. Part one in this series covers the common occurence of the Thrashing condition that happens when an Apache configuration is overtuned for its available hardware. Check out my indepth analysis including tips on how to avoid this condition and make your Apache server run the way it should.
Moving into part 3 of my Apache Performanc Tuning Series. We will cover the specific directives we should be considering when optimizing our Apache server. There are directives specific to your MPM and common to all MPMs. We will go over what these directives do and suggestions for how to configure them. We will also cover using IfModule to maintain the highest level of compatability within our Apache configs.
Part 4 of this series provides indepth instructions for how exactly to change directives on various Liquid Web system types. Just click your specific server type and follow the instructions one by one.
The hosting world’s bread & butter solution for providing high availability and redundancy is load balancing. There are many different use cases for a Load Balancer (LB). It is important to know how to effectively manage your LB configuration so that it performs optimally in your environment. The proceeding article will review some of the common practices that, when adhered to, provide a smooth and seamless high availability website/application through the use of load balancing.
The second article in my multi-part series on MySQL Performance. Published by Liquid Web, Inc on the Liquid Web Knowledge Base. This article discusses the use cases for both MyISAM and InnoDB, a widely contentous topic to be sure. Both MySQL engines have their niche and in their niche they perform very well. This article is a guide to understanding when, why and how to use MyISAM vs InnoDB.
The first in a multi-part series on MySQL Optimization written for Liquid Web, Inc. This one covers the basics of identifying bottlenecks using mysqladmin and mysql to view the MySQL process list. If you’ve been interested in optimizing your database setup, this is just the start of a longer series where I cover several topics all related to MySQL Optimization.