Understanding Container Isolation and Resource Caps
How Linux cgroups and namespace isolation guarantee that neighbor sites cannot degrade your performance.
Why Container Isolation Matters
On traditional shared hosting and pseudo-cloud platforms, dozens of websites share the same kernel process table and memory pool. If a neighboring website suffers a traffic spike, runs an unindexed SQL query, or gets compromised, all other sites on the server slow down.
Hardware-Enforced Resource Caps
Tinave enforces strict isolation using Linux kernel control groups (cgroups) and isolated namespaces:
- Dedicated Memory: Your site is allocated dedicated physical RAM. It cannot be consumed by adjacent pods.
- vCPU Execution: CPU cycles are allocated with strict priorities, preventing background worker starvation.
- Dedicated MariaDB 11 Database: Your SQL queries execute in an isolated database container with dedicated InnoDB buffer pools.
Guaranteed Stability: Even during massive traffic spikes, your TTFB remains stable because no other tenant can steal your server resources.
Was this article helpful?
Your feedback helps our team continuously improve our documentation.