Author: Build Websites

  • Overselling versus Overloading: What Is Overloading? (Part 2)

    Overselling versus Overloading: What Is Overloading? (Part 2)

    What Is Overloading?

    Overloading is when a server is so heavily populated that it begins to affect performance. Sites can run slowly or can go down entirely. This is essentially overselling on steroids.

    Most hosts that overload either do so due to willingness or incompetence.

    On one end of the spectrum, you have “hosts” (kids, amateurs, foreigners, etc) that don’t know what they’re doing. With their reseller account, VPS, or dedicated server, they simply fill up a server, unaware of what the does to sites. Their only knowledge is with using cPanel, and that’s not adequate to be a server admin. Some go a step further and offer asinine “master reseller” or “alpha reseller” plans, which cause a server to spiral out of control. Even if they wanted to, such plans remove the actual provider, and it becomes impossible to manage the hardware. There’s no way to cap usage or specify server density/population.

    On the other end, you have the greedy mega-hosts (“unlimited” hosts) that “solve” the issue of overloading by severely curtailing what can be done in an account. And it still runs slow!

     

    Unlimited Host vs. Overselling

    At the big hosts, overloading happens due to greed and an overzealous desire to turn a profit. Why only make $2,500 per server when you can make $5,000? (How do you think they pay those ridiculous commissions of $75 to $100 each?)

    If you crawl through the Terms of Service (ToS) or Acceptable Use Policy (AUP) — the fine print that nobody reads — you’ll find the draconian limits that are heavily enforced by these hosts. CPU, RAM, and MySQL queries are so low that you essentially have to run an HTML-only site, or have a site with no traffic, to avoid them.

    Some of the limits are hidden entirely, and not even found in the ToS/AUP documents! You have to dig around the internet to glean information from tickets that have been posted, and complaints online.

    The biggest reason sites run slow at large hosts is throttling. Everything is throttled. Rather than have a server that immediately responds to a request, the requests are put into a queue and loaded as resources become available. This is why, for example, a page loaded from a good host — for example, Veerotech, or EuroVPS — loads in 0.5 seconds. And why does a page from a crappy host — for example, Dreamhost, Hostgator/EIG — take anywhere from 1 to 8 seconds.

    And the first hint of overage on your part results in a suspension due to resources, paired with an upsell to their other services. At better hosts, such things don’t happen.

    It’s important to note that not all unlimited-style hosts do this. Most do — mostly because EIG owns 60+ brands — but not all. So far we’ve found SiteGround, Stablehost, and InMotion to be responsible hosts. They care more about customers than turning a profit, and it shows.

    VPS Hosts vs. Overselling

    Some hosts like to pretend a VPS cannot be oversold (and thus overloaded), but that’s simply not true. Most virtualization technologies allow for RAM overcommitment, and the older methods allow for CPU overuse.

    The most common problem technology is OpenVZ, but not because it’s necessarily bad technology. (Well, UBC/”burst” on CentOS 5 is, but not swap on CentOS 6. But that’s another story.) The real problem is again amateurs, kiddies, foreigners, etc. Thanks to dummy-friendly control panels like SolusVM, everybody likes to pretend to be a “host”, but few are experienced/seasoned server admins. So what you end up with is a node (server) that is populated with too many VPS, including not enough headroom for the server itself. If you’re not micro-managing the server regularly, it’s also easy to allow users to hog the CPU, which causes problems. OpenVZ is popular mostly because it is cheap and easy to set up/run.

    Virtuozzo is a commercial version of OpenVZ, with better RAM allocation for the end users (SLM). It suffers the same problem with CPU abuse.

    Hosts like to say that Xen, VMware, and Hyper-V cannot be oversold, but that’s not true — you can “balloon”/overcommit the RAM. KVM can overcommit both CPU and RAM.

    As with anything else, who you choose as a host is the most important factor. It’s why we use an excellent hosts like EuroVPS, LiquidWeb, and Godaddy for our important VPS projects. Some hosts promise that they do not oversell their VPS. Unlike shared/reseller hosting, this can be true! Stablehost, for example, as OpenVZ VPS plans, and makes this claim. (And it’s true! We use one at digitalFAQ.com as one of our primary servers!)

    CloudLinux and 1H Hive

    In recent years, more and more hosts have adopted CloudLinux as a tool to combat abuse on a server. Hosts can populate a server without fear of abuse because CloudLinux limits the user account to a % of CPU. The only person with a slow site is the one trying to use too many resources, usually 10%. While this doesn’t prevent a host from overselling, and thus overloading, it prevents the users from hogging the system as if it were their private dedicated server.

    The problem, however, is that some hosts are too cheap. This is commercial software that carries a monthly fee of about $10 per server. While that would be chicken feed to any host of any size, remember that these hosts are already doing everything they can to squeeze that last dime of profit out of the server. As a result, the server can run slowly and often do. When a host is not using CloudLinux or 1H Hive on their shared/reseller server, then find another host.

    Which Hosts Overload?

    The most common offenders are pretty easy to find — refer to any fake “top ten” list online, which is based purely on affiliate pay. The higher the commission, the more they cut corners on their customers. Or look up the term “slow” (i.e. Dreamhost slow), and you’ll quickly discover if that’s the case. Generally speaking, it’s those faux “unlimited” hosts that are the worst offenders: Dreamhost, Yahoo, Network Solutions, myHosting.com, etc. And then all of those EIG brands: Fatcow, BlueHost, Hostmonster, HostGator, iPage, JustHost, IXWebHosting, and many more. Again, they have 45+ brands.

     

  • Overselling versus Overloading: What Is Overselling? (Part 1)

    Overselling versus Overloading: What Is Overselling? (Part 1)

    What Is Overselling?

    Overselling is a deprived way to define resource management on servers.

    It applies to the disk space only. Specifically, it applies to the bandwidth, but in realism these days there are so many bandwidths available, that it does not matter the exterior of DDoS mitigation.

    So let us use shared hosting (aka reseller hosting) as an example. There are four concepts to be considered:

    • Customers are buying a plan that has a space of X amount.
    • Customers are using the space of X amount.
    • Servers have the space of X amount.
    • Servers are regularly upgraded to new technology, which normally has more space.

    Therefore, based on these key factors you have to manage the server: Does the entire allocation of space is used by the customer? In most cases, the reply is no. The average website comes under 1GB and acquires only modest traffic at best. To reserve the space of X amount constantly would be wastage; it would considerably drive up costs. And within that the reason for overselling lies: in retaining the costs down for customers.

    To use some number from Stablehost — an outstanding host, that is very honest and transparent — a particular server might comprise 1200GB. Their $10 plan provides 20GB and permits 60 accounts per server which are not oversold (1200/20=60). The server may bring in $600 (10 x $60), which will hardly fulfill the costs of the server. Although a home desktop is economical, think of a server with multi-core Xeon CPUs, RAID-10 SAS server-grade hard drives, and 64GB+ of RAM is not. There are also energy charges to run them for 24/7, personnel costs for support, facility costs (co-location), bandwidth, etc. Therefore, that $10 wants to be like $30 or $40 to fulfill its costs!

    Additionally, the server can only use a small portion of RAM and CPU, which is a total waste of resources. You’d be giving a high price for that thing you don’t use.

    Abruptly overselling does not sound like a corrupt thing, does it?

    Which Hosts Oversell?

    All types of hosts oversell, period. Any shared/reseller host that says something else is either lying, or they are charging an expanse corresponding to having such a service. (i.e. about $4 per GB)

    Sadly, almost all hosts hide these details from customers. They mostly refer to it as “trade secrets” or something similar gibberish. Mostly it is hidden because it is gone afar from mere overselling and entered the territory of overloading.

    If you are a reseller host, it means you can do this using your reseller account. A simple check/tick box in cPanel permits the reseller to offer extra than that is available in their account. For example, a reseller of 20GB with 20 x 2GB plans (40GB = overselling). The disadvantage to this is the host is now one level removed as a provider, and too much overselling by the reseller can affect RAM and CPU on the server! Because of this fact, it takes a good host to provide dependable reseller hosting.

    How Does Overselling Work?

    The fundamental to “overselling” — or better, however (again!) clever resource management, this is what is — is to make a balance between server resources, including CPU and RAM, disk space availability, and average customer requirements. You need to be capable keep your promises to the customer while keeping charges in check.

    Also, Stablehost has verified itself to be a truthful host, and has shared those values with us! For them, the magical number is 50%, and an accountable level of overselling is:

    • Not more than 600 customers (on average, it varies) per server. That is about 2GB each, on a server with 1200GB. It is more than double the average.
    • At least 50% of the CPU is idle, which permits for decent resources for all the sites.
    • At least 50% of the RAM is available, which again permits sites to use it as required. This comprises MySQL queries.

    If at any time a site causes these amounts to drop, Stablehost will transfer that site to another server. (Except it is grown so large that it needs a VPS, but that is a different story for another time.)

    It’s all about evaluating your hardware, evaluating your classic customer, and creating intelligent conclusions based on this data.

    Unfortunately, many hosts do not do this — particularly the “unlimited” hosts such as Godaddy, Dreamhost, and the different EIG brands (Fatcow, iPage, PowWeb, etc). What happens there is you wind up with a server that is not just oversold but overloaded. It works slowly, gets postponed for using “too many resources”, and is unsatisfying to use. In our next part (part 2), we will examine What Is Overloading? , and which hosts are the usual offenders.

  • Restore Manager: the Best cPanel Backup Solution

    Restore Manager: the Best cPanel Backup Solution

    cPanel is the best and most-used web panel around, but it’s built-in backup feature is somewhat weak and outdated. So it’s no surprise that one of the top search terms related to cPanel is “cpanel backup solutions”.

    Many users opt for R1soft, as it’s very powerful – but it’s also expensive and buggy. Worse yet, R1soft has changed owners several times in recent years, and its users have often been ignored or neglected.

    Better Features Than Both CPanel And R1soft!

    Restore Manager is essentially the best of both worlds. You get the non-costly on-server integration of cPanel, and the remote granular backup of R1soft.

    The primary weaknesses of cPanel’s own backup are that:

    • only the server admin can use it (WHM root user), and
    • only the entire account can be restored (excluding MySQL and email)

    And the primary weakness of R1soft are that:

    • the bare-metal disaster recovery rarely works well
    • disk safes can easily get corrupted
    • everything is extremely slow: the backup, the restore … even the GUI!

    REM fixes all those dilemmas, as well as adds several useful features:

    More granular: cPanel allows you to backup MySQL databases and email, but that’s it. Additionally, the restoration is often buggy. However, Restore Manager doesn’t stop at just database and email. You have granular control of files, cron job, DNS records and SSL certs. Even R1soft doesn’t have that! Best of all, the REM restore tends to be flawless and error-free.

    Better exclusions : Both the server admin (via WHM) and the users (via cPanel) can exclude content that doesn’t need to be backed up. Files types and paths (or both) can be ignored, making backups quicker and smaller. cPanel (but not WHM) natively has this function, but it’s buried in the .conf files. R1soft has it just for admins.

    Better scheduling: These days, most server admins want to use WHM, not the SSH command line (CLI). A common complaint about cPanel is that the backup scheduling is terrible. There’s no “backup now” function in WHM, and the scheduling of backups is buried. You have to enter CLI to backup on-demand, and the backup scheduler is hidden in the WHM corn configuration.

    Logging: Server admins will like this feature. Neither the R1soft plugin nor the native cPanel backup function has easy-to-find records of actions taken by users. And, as expected, low-knowledge users sometimes make false claims. For example, “the server changed my file!” – but in reality, the user restored an old copy of a file. It’s a small feature, and one that may never be needed, but it could save you a lot of effort if you’re a web host.

    Local Vs. Remote Backups In REM? (Both!)

    Although you can choose to use Restore Manager in local mode, it’s somewhat pointless, as a local backup isn’t really a backup at all. A primary benefit of REM is the ability to remotely perform an incremental backup (meaning that only changed files/databases/records are backed up), like R1soft does, and have the incremental granular restore options.

    One of my favorite aspects of Restore Manager is that the remote backup doesn’t interfere with cPanel’s native local backup, like R1soft did. Although REM is excellent, no backup solution is perfect, and a second backup can be a life-saver. Restoring local full-domain cPanel backups is also much quicker, when non-granular restoring is needed.

    How The CPanel/WHM Backup Plugin Works

    Unlike the native cPanel backup, Restore Manager is a true disaster recovery (DR) solution. And it’s superior to R1soft in speed and reliability. And it’s easy to use:

    Step 1 :Installation is well-documented at the GK~root site, and takes about 5 minutes. You’ll need root CLI/SSH access to both the cPanel server and the remote server. Adjusting settings and options takes about 10-15 more in WHM.

    Step 2 :The initial backup can take a while, depending on the site sizes. Subsequent backups are quicker. Once done, the backups can be seen in both WHM and cPanel. However, the cPanel interface has many more options, and is the suggested restore method. That’s where you’ll find the granular controls to restore individual files, mailboxes, etc.

    Step 3 :Nope, just 2 steps!

    Unlike R1soft, the REM GUI is extremely intuitive. You shouldn’t have any issue figuring it out.

    In case of full DR, meaning the old server has imploded or been eaten by zombies, simply refer to the online documentation. It’s just like R1soft, but faster! A few clicks in the new WHM instance (on a new server) is all it takes.

    GK~Root’s Quality Support, Documentation, Pricing

    One area where cPanel does decent, and R1osft completely sucks, is in the support department. And GK~root is just as good as cPanel’s ticket system. In fact, in 2016, they’re better than cPanel!

    We’ve used REM off and on for several years now. Earlier versions of REM were extremely buggy, and not fit for production environments. And back then, it would often take weeks to get answers to support tickets. The support quality was always good, just not the speed. So if you previously used GK~root, and your experience was also dismal, give them another chance. We did. Since 2015, both support speed and quality has been excellent – assuming you ever need it, as the products are excellent.

    The GK~root on-site documentation is also excellent, with no detail left out. My biggest complaint about R1soft is the documentation is a joke, and cPanel often forgets that many panel users are mere mortals (that speak regular English) and not IT nerds (that speak techie blah-blah).

    And the most amazing things of all? The REM license only costs $27 per year. Most alternative options cost that much monthly! They even give volume discounts, as if it wasn’t low-cost enough! (For the truly skittish or cheap, they also have $3 monthly licenses.)

    It’s Not Perfect … But It’s Close!

    The only real “flaw” of REM is simply due to the nature of how its backup system works. You can push backups, or you can pull backups. REM pushes, so if the server was ever compromised, the hacker could also get access to the backup server. cPanel pushes, and REM is based on the cPanel backup system. R1soft, by contrast, pulls.

    However, after having struggled with quality backups for years and years, REM just works. I don’t know what else to say. If you’re not convinced that

    • it’s quality
    • with excellent support
    • that costs almost nothing

    … then I can only assume that you’ve never screamed at the monitor (cPanel backups), dealt with R1soft implosions (and cried and whimpered over your keyboard), or just generally hit your heads against the wall (Bacula, cPRemote, and other crappy scripts). Learn from my mistake … or don’t.

    GK~root’s Restore Manager now powers all of our non-primary cPanel systems. It cut time, it cut costs. We highly suggest it!