Too many addon domains can slow down cPanel or create problems

[Gino Viroli]

I actually resell hosting plans by using one single cPanel account and many addon domains under it.

Basically for each new user I don't cerate a new cP account, but I simply create a new ADDON domain and give him the necessary space.

I know in this way the final user won't be able to manage his emails and he want be able to access all cPanel features, but that's ok.

My only question is: "is there a limit on the number of cPanel addon domain that can be added?".
I'm allowed to add unlimited addon domains, but is there something that might happen that slows down cPanel or could create problems?

I mean is there any suggestions the kind cp's sw engineers could give me about the way i'm using cPanel which might not be the usual way of using it. (As for instance: "be aware that Awstast could run very slow or crash", or "be aware that mails from different addon domains under the same cp account could create many problems.", etc.)

Many thanks!

[xprt5]

The only limits would be kernel or file system limits such as descriptors, inodes or characters.

Theoretically its unlimited but the OS or File system has limitations that will be reached at some point, these are not cPanel limitations.

The more addon domains, parked domains or subdomains you continue to add to one account the longer it will take Apache to load the config file as it has to parse thru the config one line at a time then load corresponding data or files. This will continue to cause longer startup times.

You would be wise to break up the addon domains among multiple users to spread out the configuration.

[Gino Viroli]

1st of all, thanks for the reply!
Below are my comments.

The more addon domains, parked domains or subdomains you continue to add to one account the longer it will take Apache to load the config file as it has to parse thru the config one line at a time then load corresponding data or files. This will continue to cause longer startup times.

But wouldn't it be the same when creating standard cPanel account for each new user instead of ADDON domains?
I mean, isn't there a config file also for standard cP account when adding more domains on same server (even if in different cP accounts), so Apache would have to look into it in the same way it does for ADDON domains, wouldn't it?!

You would be wise to break up the addon domains among multiple users to spread out the configuration.

Could you plz explain this? What do you mean by breaking up addon domains?
Each of my user needs is own domain/emails.
I created one cP account, then I placed all addon domains in subfolders of such account.
I have an .htaccess for the main cP accunt that contains config shared among all addon domains, then I have single .htaccess files for each addon domains if they need particular configurations.

[Spiral]

Bigger question ---

Why in the world are you using Cpanel instead of WHM?

Forget about the performance complications, just think about the security complications, or worse the possible nightmare of keeping up and managing that.

I just can't see any practical purpose of doing what you are doing and I am just curious as to what your reasoning or rational is being it ????

[nibb]

I suppose he is using a single "unlimited" hosting account and reselling from it.

The only problem I think that can happen is probably the interface taking longer to load then usual. You said it should be the same as adding normal accounts. Well first no. It isnt.

WHM shows account in a bunch and is made to manage multiple account and records. Addons domains, im not sure what would be the limit until the interface takes to long to show.

The other think that will probably slow down is the apache config, the more data you add, that means addon records, the more it will take to load.

It all depends on hardware and how many you have. Just take into account its not made for that. Addon domains are not replace WHM and real accounts. They are just addons. So said that, I dont think its tested for to massive domain addons as its not the usual or proper way to use it. Its best to test it on your own and see when things slow down.

[Gino Viroli]

Bigger question ---
Why in the world are you using Cpanel instead of WHM?

Thanks for the interest in my question, the reason is simple, and it's not to be cheap and not buy a WHM. I have WHM, but in place of creating dozens of cP accounts, one for each customer, I rather prefer creating one single account cP and dozens addon domains under it.

Why am I doing this?

Because everytime cP comes out with an update something gets screwed up in interface! Now fixing one cP is much easier than checking dozens of them to see if they work.
Moreover I like to set in the public_html folder my php.ini configuration that recursively is applied to all folders under it. Since addon domains are created in subfolders of the public_html they get already set up with the proper php.ini configuration I need.

I don't know how to explain, it's much easier to manage the all thing. I even have only one control panel to manage everything instead of switching around among WHM and dozens of cP accounts.

[Gino Viroli]

Thanks nibb, my replies below:

The other think that will probably slow down is the apache config, the more data you add, that means addon records, the more it will take to load.

Sorry for the ignorance, but when you talk about Apache config do you mean thet single .htaccess loaded under each addon domain?Or do you mean the main httpd.conf of Apache (I can not access it, coz' I'm on a reseller account).

I dont think its tested for to massive domain addons as its not the usual or proper way to use it. Its best to test it on your own and see when things slow down.

I definitely agree on this, that's why I was asking for suggestions.

[Gino Viroli]

Any other ideas/suggestions?!?!

[Cyberdave]

This is an interesting conversation but it sounds like a monumentally bad idea. At some point the customers will think there is something wrong with your hosting service for being too slow etc and jump ship! Also I wonder if the host provider being resold would consider this a violation of TOS?