Resource Allocation

We have a number of limitations in place that are applied to all hosting plans. This is done in order to ensure fair resource usage.


Resolve problems due to high resource usage

A relatively common issue is high MySQL usage because your account's site or sites receive a lot of traffic. In other words, your site is popular, which is good news!

However, in other cases, high CPU usage from database processing is unintentional and caused by other factors. The following list describes some common software issues that can cause high CPU usage from database processing. Resolving these issues does not require an upgrade:

  • Recent changes to the website may have included database queries that are too resource-intensive.
  • Another cause can be “plug-ins” for a content management system or other application. If you have activated any plug-ins recently, it is worth trying to disable them temporarily to see if the issue resolves.
  • Running cron jobs too frequently—particularly resource-intensive cron jobs—can negatively impact MySQL performance. Only run cron jobs as often as necessary.
  • Comment spam on a forum or blog such as Wordpress can affect MySQL usage. Check your account for any old installations that you can remove, or for comments and spam postings that look automated.
  • Search engine spiders “crawl” your website. If this occurs too frequently, performance may be affected. Please make sure that your robots.txt file contains a Crawl-delay setting of 30 seconds or higher. For example:
    User-agent: *
    Crawl-delay: 30
  • A hacked account often causes abnormal MySQL usage. Make sure you use a secure password and keep all software up to date. For information about how to secure a hacked site, please see this article.
  • Make sure you keep all installed web applications up to date.

Shared Web Hosting

Processes

Processes invoked by the web server, cron, shell or any other method should not exceed the following limitations:

  • Consume more than 256 MB of memory space.
  • a maximum of 25% CPU usage limit. You may exceed this limit for no longer than 60 seconds. It is unlikely that you hit the 25% CPU usage. Unless your site is script intensive and requires more processing.
  • Number of open files should not exceed 64.
  • Create core dumps.
  • Use the find command, or any similar tool which recursively explores directory structures, anywhere except in their own directories.
  • Number of simultaneous processes should not exceed 25.
  • Execute a script/binary that forks in a way to create a fork bomb.
  • Programs may not run in the background or listen on a network port. If you require a bot, service or daemon, you should consider a dedicated server, as very few shared web hosts allow this type of program.

Database Restrictions

  • All users are restricted to 20 concurrent MySQL connections.
  • Each database is restricted to 2 GB of disk space.
  • Database queries should not exceed 5,000 per hour.
  • Database changes (insert/update/delete) should not exceed 2,500 queries per hour.
  • Database servers should not be used as a hosted solution. Database access should only be used for the web site hosted by Woktron Web Hosting
  • Databases may not be accessed by externally hosted sites, except for the purposes of administering the database.

If you have reached the MySQL Database size limit and all of the data in the database is needed for your website, you can consider an upgrade to a higher plan where the MySQL Database size limit would suite your needs.


Files and Directories

An inode is a data structure used to keep information about a file on your hosting account. The number of inodes indicates the number of files and folders you have. This includes everything on your account, emails, files, folders, anything you store on the server. Each file (a webpage, image, email, php file, directory, etc.) on your account uses up one (1) inode.

The total number of inodes in an account is limited as follows:

  • STARTER: 100.000
  • SMART: 150.000
  • PREMIUM: 250.000

This is not something we actively enforce and it will only become an issue if a client is causing problems for other users on the server.

  • Accounts exceeding 250,000 inodes may be removed from our backup system.
  • A directory can not contain more than 2,500 immediate child files. This includes subdirectories themselves, but does not include files contained within those directories.

Email and Mailing Lists

  • Attachments in excess of 25 MB should not be sent via email.
  • Processes should not send outbound mail to more than 25 recipients at any given time.
  • POP connections are limited to 60 per hour.
  • IMAP connections are limited to 120 per hour.
  • SMTP connections (outbound email connections) are limited to 500 per hour.
  • The maximum number of members per mailing list is 1,500.
  • Mailing lists larger than 1,500. Dividing one list into smaller parts to get around this limit is not allowed.
  • Any mailing list over 900 emails is only allowed in off peak times such as Saturday and Sunday or from 1am to 8am ET during the week.
  • Any mailing list must be throttled so that it sends an email every 6 seconds at the very minimum. If the mailing list software you are using doesn't support throttling you must use something else. We do this as this keeps the server load from going very high and causing problems for other users. If you don't do this you will be suspended.
  • We do not allow you to send to a mailing list you were given or that you bought. This is spamming and we have zero tollerence for this.
  • Any mailing list must comply with the rules set forth by the European Union and can be found at: https://ec.europa.eu/info/law/law-topic/data-protection_en.
  • No Direct SMTP mailing system scripts are permitted. Mail should be relayed through the local MTA.

Cron Jobs

  • All cron jobs must be 'niced' to 15 or greater (see the Unix manpage for "nice" for more information).
  • Setting up more than 5 simultaneous cron jobs is prohibited
  • Consume more than 30 seconds of CPU time per execution (realtime).
  • A cron job should not execute more frequently than once every 15 minutes.


Enterprise Web Hosting

Processes

Processes invoked by the web server, cron, shell or any other method should not exceed the following limitations:

  • Consume more than 256 MB of memory space.
  • a maximum of 25% CPU usage limit. You may exceed this limit for no longer than 60 seconds. It is unlikely that you hit the 25% CPU usage. Unless your site is script intensive and requires more processing.
  • Number of open files should not exceed 96.
  • Create core dumps.
  • Use the find command, or any similar tool which recursively explores directory structures, anywhere except in their own directories.
  • Number of simultaneous processes should not exceed 25.
  • Execute a script/binary that forks in a way to create a fork bomb.
  • Programs may not run in the background or listen on a network port. If you require a bot, service or daemon, you should consider a dedicated server, as very few shared web hosts allow this type of program.

Database Restrictions

  • All users are restricted to 50 concurrent MySQL connections.
  • Each database is restricted to 5 GB of disk space.
  • Database queries should not exceed 10,000 per hour.
  • Database changes (insert/update/delete) should not exceed 5,000 queries per hour.
  • Database servers should not be used as a hosted solution. Database access should only be used for the web site hosted by Woktron Web Hosting
  • Databases may not be accessed by externally hosted sites, except for the purposes of administering the database.

Files and Directories

An inode is a data structure used to keep information about a file on your hosting account. The number of inodes indicates the number of files and folders you have. This includes everything on your account, emails, files, folders, anything you store on the server. Each file (a webpage, image, email, php file, directory, etc.) on your account uses up one (1) inode.

The total number of inodes in an account is limited as follows:

  • CORE: 300.000
  • PROFESSIONAL: 400.000
  • ENTERPRISE: 500.000

This is not something we actively enforce and it will only become an issue if a client is causing problems for other users on the server.

  • Accounts exceeding 500,000 inodes may be removed from our backup system.
  • A directory can not contain more than 2,500 immediate child files. This includes subdirectories themselves, but does not include files contained within those directories.

Email and Mailing Lists

  • Attachments in excess of 25 MB should not be sent via email.
  • Processes should not send outbound mail to more than 25 recipients at any given time.
  • POP connections are limited to 60 per hour.
  • IMAP connections are limited to 120 per hour.
  • SMTP connections (outbound email connections) are limited to 500 per hour.
  • The maximum number of members per mailing list is 1,500.
  • Mailing lists larger than 1,500. Dividing one list into smaller parts to get around this limit is not allowed.
  • Any mailing list over 900 emails is only allowed in off peak times such as Saturday and Sunday or from 1am to 8am ET during the week.
  • Any mailing list must be throttled so that it sends an email every 6 seconds at the very minimum. If the mailing list software you are using doesn't support throttling you must use something else. We do this as this keeps the server load from going very high and causing problems for other users. If you don't do this you will be suspended.
  • We do not allow you to send to a mailing list you were given or that you bought. This is spamming and we have zero tollerence for this.
  • Any mailing list must comply with the rules set forth by the European Union and can be found at: https://ec.europa.eu/info/law/law-topic/data-protection_en.
  • No Direct SMTP mailing system scripts are permitted. Mail should be relayed through the local MTA.

Cron Jobs

  • All cron jobs must be 'niced' to 15 or greater (see the Unix manpage for "nice" for more information).
  • Setting up more than 5 simultaneous cron jobs is prohibited
  • Consume more than 30 seconds of CPU time per execution (realtime).
  • A cron job should not execute more frequently than once every 15 minutes.


Reseller Web Hosting

Reseller accounts are subject to the same limitations as our Shared Web Hosting accounts, however, the limit in this case is counted per DirectAdmin user account, not for the entire reseller package. The only exception to this is the Inode limitation.


Processes (for each user)

Processes invoked by the web server, cron, shell or any other method should not exceed the following limitations:

  • Consume more than 256 MB of memory space.
  • a maximum of 25% CPU usage limit. You may exceed this limit for no longer than 60 seconds. It is unlikely that you hit the 25% CPU usage. Unless your site is script intensive and requires more processing.
  • Number of open files should not exceed 64.
  • Create core dumps.
  • Use the find command, or any similar tool which recursively explores directory structures, anywhere except in their own directories.
  • Number of simultaneous processes should not exceed 25.
  • Execute a script/binary that forks in a way to create a fork bomb.
  • Programs may not run in the background or listen on a network port. If you require a bot, service or daemon, you should consider a dedicated server, as very few shared web hosts allow this type of program.

Files and Directories (global setting for each reseller package)

An inode is a data structure used to keep information about a file on your hosting account. The number of inodes indicates the number of files and folders you have. This includes everything on your account, emails, files, folders, anything you store on the server. Each file (a webpage, image, email, php file, directory, etc.) on your account uses up one (1) inode.

The total number of inodes in an account is limited as follows:

  • SILVER: 250.000
  • GOLD: 500.000
  • PLATINUM: 1.000.000

This is not something we actively enforce and it will only become an issue if a client is causing problems for other users on the server.

  • Accounts exceeding 1.000,000 inodes may be removed from our backup system.
  • A directory can not contain more than 2,500 immediate child files. This includes subdirectories themselves, but does not include files contained within those directories.

Database Restrictions (for each user)

  • All users are restricted to 20 concurrent MySQL connections.
  • Each database is restricted to 2 GB of disk space.
  • Database queries should not exceed 5,000 per hour.
  • Database changes (insert/update/delete) should not exceed 2,500 queries per hour.
  • Database servers should not be used as a hosted solution. Database access should only be used for the web site hosted by Woktron Web Hosting
  • Databases may not be accessed by externally hosted sites, except for the purposes of administering the database.

Email and Mailing Lists (for each user)

  • Attachments in excess of 25 MB should not be sent via email.
  • Processes should not send outbound mail to more than 25 recipients at any given time.
  • POP connections are limited to 60 per hour.
  • IMAP connections are limited to 120 per hour.
  • SMTP connections (outbound email connections) are limited to 500 per hour.
  • The maximum number of members per mailing list is 1,500.
  • Mailing lists larger than 1,500. Dividing one list into smaller parts to get around this limit is not allowed.
  • Any mailing list over 900 emails is only allowed in off peak times such as Saturday and Sunday or from 1am to 8am ET during the week.
  • Any mailing list must be throttled so that it sends an email every 6 seconds at the very minimum. If the mailing list software you are using doesn't support throttling you must use something else. We do this as this keeps the server load from going very high and causing problems for other users. If you don't do this you will be suspended.
  • We do not allow you to send to a mailing list you were given or that you bought. This is spamming and we have zero tollerence for this.
  • Any mailing list must comply with the rules set forth by the European Union and can be found at: https://ec.europa.eu/info/law/law-topic/data-protection_en.
  • No Direct SMTP mailing system scripts are permitted. Mail should be relayed through the local MTA.

Cron Jobs (for each user)

  • All cron jobs must be 'niced' to 15 or greater (see the Unix manpage for "nice" for more information).
  • Setting up more than 5 simultaneous cron jobs is prohibited
  • Consume more than 30 seconds of CPU time per execution (realtime).
  • A cron job should not execute more frequently than once every 15 minutes.


Virtual Private Servers

You are allowed to use 100% of your assigned CPU resources.

However, this is only a portion of the server's total CPU resources. If you require more CPU resources you should choose a Dedicated Server instead.



Dedicated Servers

You are allowed to use 100% of the server's CPU resources.

  • 0 Users Found This Useful
Was this answer helpful?

Related Articles

How to cancel your web hosting plan

You can cancel your service from within your Client Area Control Panel. Login to our client...

How do I upgrade my web hosting plan or VPS?

Upgrading is made very easy with the system we have setup. To upgrade your account to another...

When will I receive my invoice?

IMPORTANT: Your invoice will be sent to the e-mail address you registered with, so it is very...

Why was my order blocked?

Here at Woktron Web Hosting we take fraud very seriously. We have an automated system in place to...

Money back guarantee

If for any reason you are unsatisfied with our service within the money back guarantee period,...