InMotion Hosting Puts Owned Infrastructure Advantage to Work, Deploys TCMalloc Across Entire Shared Hosting Fleet

A fleet-wide TCMalloc deployment ends gradual MariaDB memory growth on InMotion’s shared servers. Customers benefit with zero changes required. VIRGINIA BEACH, Va., May 11, 2026 /PRNewswire/ —ย InMotion Hosting announced the successful fleet-wide deployment of TCMalloc, an open-source memory management tool originally developed by Google, across its shared hosting servers. The change replaces the default memory…


InMotion Hosting Puts Owned Infrastructure Advantage to Work, Deploys TCMalloc Across Entire Shared Hosting Fleet

A fleet-wide TCMalloc deployment ends gradual MariaDB memory growth on InMotion’s shared servers. Customers benefit with zero changes required.

VIRGINIA BEACH, Va., May 11, 2026 /PRNewswire/ —ย InMotion Hosting announced the successful fleet-wide deployment of TCMalloc, an open-source memory management tool originally developed by Google, across its shared hosting servers. The change replaces the default memory tool that ships with Linux and addresses a long-standing database problem that has caused website crashes and slowdowns industry-wide. The rollout is already making a noticeable difference in performance reliability for customers.

What TCMalloc is, and Why it Matters
Every server uses a memory allocator, a low-level tool that decides how programs store and release memory while they run. Most Linux servers rely on the default allocator that ships with the operating system, called glibc malloc. It works for most things, but it has a known weakness: under sustained database workloads, it tends to hold onto memory that should have been released, and that memory piles up over time.

TCMalloc, built by Google for its own high-traffic services, handles this job differently. It keeps memory organized more efficiently and returns unused memory to the operating system more predictably. For databases that run 24/7 under heavy load, that difference is significant.

The Problem Customers Were Experiencing (Even if They Didn’t Know It)
Most websites store content, like blog posts, products, and user accounts, in a database. On shared hosting, a single server runs the database software for many websites at once. If that database runs into an issue, every website on that server feels it.

MySQL and MariaDB are the databases that power a large share of the web, including WordPress sites, ecommerce platforms, and SaaS applications. On a typical shared server, database memory usage climbed steadily until it exceeded a critical limit. The server would then force a crash to recover, and the cycle would repeat. This resulted in websites going offline, loading slowly, or throwing errors until the database came back up. For years, hosting companies have blamed this on the database itself.

InMotion’s engineers took a closer look. They saw the real problem was rooted in the default memory allocator. The Systems team replaced it with TCMalloc fleet-wide. The fragmentation pattern that had been driving up memory usage disappeared.

“Gradual MySQL memory growth usually looks like a database leak. But the real problem sits one layer deeper in the memory allocator,” explains Sean Combs, Tier 3 Systems Administration Technical Team Lead at InMotion Hosting. “Switching to TCMalloc gave our shared servers predictable memory behavior and removed an entire class of incidents that most providers can’t usually address at the infrastructure level.”

Source link