GoAdmio
GoAdmio Documentation

Initial Quota Setup

From the GoAdmio knowledge base.

Initial Quota Setup

This page explains the Initial Quota Setup in the GoAdmio Admin Panel. It defines the default resource limits applied to newly created hosting accounts when a package does not override them.

Location: Admin Panel → Server Management → Initial Quota Setup


Overview

The Initial Quota Setup page sets the baseline resource limits for new accounts. Think of it as the "default package" that applies when an account is created without a specific package, or when a package leaves a limit unset.

These limits protect the server from a single account consuming all available resources. They are enforced at the account level and apply to CPU, memory, concurrent connections, and MySQL query throughput.

> Note: Limits set here can be overridden per account via Add/Modify Packages or Modify Account. If you assign a package at account creation, the package limits take precedence.


Resource Presets

The page offers three preset profiles to start from:

| Preset | Intended for |
|---|---|
| Unlimited | No resource caps. Suitable only for trusted accounts or dedicated environments. |
| Standard (Shared Hosting) | Balanced limits for typical shared hosting accounts. Recommended default. |
| Starter (Personal Websites) | Tighter limits for small personal sites and low-traffic accounts. |

Selecting a preset fills the fields below with the corresponding values. You can then fine-tune individual limits.

> Warning: Choosing Unlimited removes all resource caps for new accounts. On a shared server this can allow one account to degrade performance for all others. Use only when you fully trust the account owner.


Quota Fields

Quota Status

Enables or disables quota enforcement for new accounts. When disabled, the limits below are not applied.

| Value | Meaning |
|---|---|
| Enabled | Resource limits are enforced for new accounts. |
| Disabled | New accounts are created without resource caps. |


Memory Limit

The percentage of total server memory a single account may consume.

| Field | Description | Example |
|---|---|---|
| Memory Limit | Percentage of total RAM allowed per account. | 100 (%) |

> Note: A value of 100 means the account can use up to the full server memory if available. On shared servers, lower values (e.g., 25–50) are recommended to prevent a single account from starving others.


CPU Limit

The percentage of total CPU a single account may consume.

| Field | Description | Example |
|---|---|---|
| CPU Limit | Percentage of total CPU allowed per account. | 100 (%) |

> Tip: For shared hosting, a CPU limit between 25 and 50 is typical. Set to 100 only for trusted or dedicated accounts.


MAX_USER_CONNECTIONS

The maximum number of concurrent MySQL connections a single database user may open.

| Field | Description | Example |
|---|---|---|
| MAX_USER_CONNECTIONS | Maximum simultaneous MySQL connections per user. | 0 |

> Note: A value of 0 means no limit (MySQL default). Set a positive value to cap concurrent connections per user.


MAX_QUERIES / HOUR

The maximum number of SQL queries a user may execute per hour.

| Field | Description | Example |
|---|---|---|
| MAX_QUERIES / HOUR | Maximum SQL queries per user per hour. | 0 |

> Note: A value of 0 means no limit. Set a positive value to cap hourly query volume. This is useful for preventing runaway scripts from exhausting database resources.


MAX_UPDATES / HOUR

The maximum number of SQL UPDATE statements a user may execute per hour.

| Field | Description | Example |
|---|---|---|
| MAX_UPDATES / HOUR | Maximum SQL UPDATE statements per user per hour. | 0 |

> Note: A value of 0 means no limit. Set a positive value to prevent write-heavy scripts from degrading database performance.


How to Configure

  1. Log in to the GoAdmio Admin Panel.
  2. Navigate to Server Management → Initial Quota Setup.
  3. Choose a preset (Unlimited, Standard, or Starter) or configure each field manually.
  4. Set Quota Status to Enabled to apply the limits.
  5. Click Save.
New accounts created after saving inherit these limits. Existing accounts are not affected unless you modify them individually.

How Limits Are Applied

| Scenario | Which limits apply |
|---|---|
| Account created with a package | Package limits override Initial Quota Setup |
| Account created without a package | Initial Quota Setup limits apply |
| Account created with a package that leaves a limit unset | Initial Quota Setup value applies for that field |
| Existing account | Not affected by changes here — use Modify Account |


Recommended Values

| Server type | Memory | CPU | MAX_USER_CONNECTIONS | MAX_QUERIES/HOUR | MAX_UPDATES/HOUR |
|---|---|---|---|---|---|
| Shared hosting (many accounts) | 25–50% | 25–50% | 10–25 | 50,000–100,000 | 10,000–25,000 |
| Starter / personal | 15–25% | 15–25% | 5–10 | 25,000–50,000 | 5,000–10,000 |
| Trusted / dedicated | 100% | 100% | 0 (unlimited) | 0 (unlimited) | 0 (unlimited) |

> Tip: Start conservative. You can always raise limits for specific accounts via packages or Modify Account.


Related Pages

Troubleshooting

| Problem | Likely cause | Solution |
|---|---|---|
| New accounts hit limits immediately | Limits set too low | Raise Memory/CPU values or assign a higher-limit package |
| Database queries failing | MAX_QUERIES/HOUR or MAX_USER_CONNECTIONS too low | Increase limits or set to 0 for unlimited |
| One account slows the whole server | Quota Status disabled or limits set to Unlimited | Enable Quota Status and apply Standard preset |
| Changes not affecting existing accounts | Initial Quota Setup only applies to new accounts | Use Modify Account for existing accounts |


Last updated: 2026-11-08

↑