RAM usage in Reseller Accounts

Portal Home > Knowledgebase > Articles Database > RAM usage in Reseller Accounts

Posted by nokhost, 02-17-2013, 09:22 AM
Hello WHT, What does the RAM usage do with hosting? Is it important? Whats the min and Max? Ok, I dont understand this factor in hosting, could you please let me know Thanks
Posted by mummy, 02-17-2013, 10:00 AM
Two posts about the same thing? http://www.webhostingtalk.com/showthread.php?t=1238656
Posted by SSD-Greg, 02-17-2013, 12:32 PM
Ram is what makes your site run smoothly its what takes the bumps off the road. If you abuse your ram usage then your host will suspend your account quick with out letting you know and sometimes hosts would celery your account with no back up.
Posted by Server Management, 02-17-2013, 12:41 PM
Some hosts allow upto 32MB but generally 64MB is likely most popular these days then the odd few will allow 128MB But if your going to need a bit of ram all the time rather then short bursts here and their you might be better asking the provider if they can give you some controlled ram resource.
Posted by Tuguhost, 02-18-2013, 04:09 AM
What I know ezpz allow burst ram to 1 gb and hostingcove allow burst to 256 mb What I think you mean about ram usage in cloudlinux ? If right that doesn't too important because even the limit is generous u can't use them for a long time
Posted by domaincart, 02-18-2013, 06:32 AM
We have reseller hostings on a provider. They don't allow to use more than 10% of server ram. So if any web site used when they suspend it. For example; if your web site get many hit when it can be use many ram. But there are many reasons of increasing ram usage.
Posted by nokhost, 02-18-2013, 12:18 PM
thanks everyone for your infomation... good to know about EZPZ. it wasnt cloudlinux,
Posted by SPINIKR-RO, 02-18-2013, 12:47 PM
We were allowing the default 1GB but we started getting mass account registrations for resellers, they would open 5-15 cPanel accounts and all run the same scripts, amazon scrapers, etc. This was mostly stopped immediately, but still annoying. We lowered to 256 (which is still a heck of a lot for shared hosting) and it has been much quieter.
Posted by Trip, 02-18-2013, 04:29 PM
That all depends on what you know... As just 2 examples, Cartika allows 256MB on their cPanel stuff and FluidHosting has elastic limits (practically none), they limit on other metrics. So you can definitely find higher end stuff than most would lead you to believe. Just have to look in the right places.
Posted by Server Management, 02-18-2013, 04:51 PM
I was referring to PHP memory limits...
Posted by Trip, 02-18-2013, 05:08 PM
And the OP was looking for total RAM.
Posted by Server Management, 02-18-2013, 05:13 PM
PHP memory limits are far more important than anything in the likes of CloudLinux since that's just to stop resource hogging where PHP limits will determine if your site will run or not...
Posted by Trip, 02-18-2013, 05:18 PM
That's good to note! And if you had prefaced your initial post with that, I think it would have been more clear that's what you were referring to. At least for me, anyways. All's well, now, though!
Posted by nibb, 02-18-2013, 08:01 PM
To be honest, I did some several tests and 32 MB works for almost anything, vbulletin, blogs, etc. I could make or create an error for almost anything with 32 MB except some very weird cases. 64 MB is safe, and I don´t know a single app that would not work with 128 MB. If any software or PHP page needs more than 100 MB RAM per execution then the problem is in the code, its just awfully wrong and badly coded. Or its not just a PHP page anymore, but a software or platform just should not fit shared hosting anyway. Shared hosting is for websites. For websites and almost all popular scripts, and software, 64 MB is more than fine. Take into account that its not per account, but every single execution would need to allocate this, even while memory is efficient in shared process, how much traffic do you think the server or account would sustain if you allow 100 MB for every single execution... You cannot pretend to use a shared host as a your own APP server, there are VPS for that. A hosting that allows 128 MB or more per account in shared hosting is only asking for troubles. Unless you only have a dozens accounts per server, its not sustainable in the long run, all you need is one users with some decent traffic and he will kidnap all RAM for himself. People that complain or need more limits than usual, are running things which are far from a website, and usually need to be accommodated into its own VPS or server.
Posted by Trip, 02-18-2013, 08:45 PM
I don't disagree, nibb, but tell that to some hosts and I wonder what they'd have to say about it... here's a reply I got from Andrew at Dathorn on the subject via email:And I think you'd agree that Dathorn is probably one of the best shared cPanel resellers ever to cross WHT (our friend the Search button backs me up here). So, clearly, it's doable. Wouldn't you think? Or have I misinterpreted something?
Posted by nibb, 02-18-2013, 09:07 PM
That is not related to the memory in PHP. You are confusing things. What he said is that the account is limited in total to 1 GB RAM, if that is true he would be hosting tops 40 Resellers or so per server. The limit in PHP for scripts is what I was talking about. All scripts you consume will go to the total RAM usage, in case of what Dathorn replied. But if PHP settings are at 128 MB and your code is bad, then you would have 10 executions in parallel to use your 1 GB, that is bad. If the limit was at 64 MB you could handle twice as much traffic on the same 1 GB. What you can consume on a reseller account or per account is completely different on what limits are set per PHP execution. Also, what he said is not really completely true. A reseller is just an internal account in WHM. CloudLinux lets you put limnits per account, not per Reseller account. Now if he was mentioning having 1 GB RAM per each account, that would mean he can host more or less 40 to 45 cPanel accounts in total per server. Not Reseller accounts, not domains, but cPanel accounts. Now depending on their costs this can be or not true. But that is very low, A reseller that has 20 accounts per server does not need a reseller account. Unless they give him multiple reseller account in multiple servers. 1 GB RAM limit per account is just abysmal, why get a VPS then if you can get a shared account with 1 GB RAM? Again this is not related to the memory limits in PHP which I was talking before.
Posted by Trip, 02-18-2013, 09:31 PM
Gotcha. I was confusing what you were talking about with what I was thinking about. Very, true. Yet, irrespective of what the php limit is, I would think a generous account limit would still be nice to have overall, if for nothing more than to know that what is guaranteed to you is more than you will ever need to use in most cases. That should promote stability, no?I'd infer you might've misinterpreted what he said about cloudlinux; he probably knows most or all of what it can and cannot do, given his position and his company's prowess up to now. As to whether a particular amount of resources are "absurd", perhaps such policies and the resulting account density may simply just be a good thing, at least for them? The way I see it, it really has nothing to do with whether or not someone should or shouldn't move to a VPS, at least in regards to them. In general, yes, the feature sets of most competitors' product lines may suggest that to be the case, but perhaps it's a little harsh to generalize in this case?
Posted by nibb, 02-18-2013, 10:01 PM
Of course its nice to have higher limits but it depends on the price you are willing to pay for them. Huge limits for unrealistic costs is another story. A hosting company needs to make money, they cannot afford to give things for free. More resources means more prices, and someone must be paying them. Everything has a limit. So it all depends on the price the customer is willing to pay for it. Usually a company will try to balance resources to match what the customer is paying for them. Some afford to lost a bit per account, but its not a long strategy for a business in the long run. Because you will only attract that type of users, that know they get more for less, and eventually you will need to raise costs or lower limits. If you read some WHT posts here, and when other fellow members ask the budget they are willing to spend on what they look, some replies are just ridiculous in what people to expect to pay and get for that money.
Posted by Dathorn-Andrew, 02-18-2013, 10:04 PM
I was pretty clear on that in my reply that Trip posted. I even stated pretty much the same thing if you re-read it. The CloudLinux limitations are per cPanel account. For us, the CloudLinux RAM limit is nothing more than a precaution that helps further prevent accounts from utilizing all available RAM when a poorly written script goes haywire. That does not mean that we allow every cPanel account to actually use 1GB of RAM on a continual basis. It is just another layer of protection. PHP memory limits are a whole different story. This limit defaults to 128MB on all of our servers. Like many hosts, it is easily changed (increased) via .htaccess or a custom php.ini file. Keep in mind that this is just a limit, most scripts won't use more than a couple MB. I do agree with most of nibb's first post. Virtually any script should have no problems running with a 32MB or 64MB PHP memory limit. There are rare occassions where a 128MB or higher limit is necessary but these would be one-time tasks such as upgrades, imports, or some other data processing.
Posted by nibb, 02-18-2013, 10:17 PM
Great. I misunderstood the post them. Yes CloudLinux is per account and I assume a reseller has multiple account so the limits is per account. Good to know what you said about the 1 GB RAM limit. Because I guess some people here would assume they could use that 1 GB all the time, 24/7. So it just a safe limit to avoid poorly scripts, but it does not mean every account can use that for a long period of time. Thanks for posting.
Posted by shqipo, 02-18-2013, 10:45 PM
Are you sure about ezpz's burst to 1GB?
Posted by Trip, 02-18-2013, 11:18 PM
Good points, all around! And thx for chiming in, Andrew! and yeah, that email I sent was Re: this thread, so I figured I'd ask one of the older games in town, hope you didn't mind me quoting your words
Posted by nokhost, 02-19-2013, 01:02 AM
I will call ezpz tomorrow and ask them
Posted by shqipo, 02-19-2013, 01:06 AM
You can't call them, you can only email them - but they're generally quite good at responding quickly. I asked because I haven't had that kind of experience: one of my sites would get shut down cause I had a WordPress script making site backups. Apparently that was too much of a load for them And it's a fairly small site, no forum, not a lot of content.
Posted by nokhost, 02-19-2013, 01:08 AM
they have a phone number on their site for pre-sale. I hope thats correct number
Posted by nibb, 02-19-2013, 02:15 AM
Burst just means for a very short period of time. Backups are not RAM intensive. They are CPU and disk intensive. For example if you are compressing the backup, this will try to use the full CPUs, and its very, very CPU intensive. Administrators will see this on cPanel as well when someone is going a backup. Its also intensive on the drives. I wonder how offend was your script running for the Wordpress backup, because I can honestly understand if that was intensive. Still this posts is about ram or memory, you could had bumped into other problems with your sites, like CPU.