Entry Processes High
Jamroom Hosting
Ken_Rich:He's got it set to 40 now. There was lot's of disagreement over what the number really means, but at least it's doubled now.
In the Jamroom hosting, what is the limit on EP? My understanding is there should be some kind of limit to foil DOS attacks. Also on shared servers, it prevents one site from hogging all the resources from the others.
Am I to understand that Jamroom hosting is not shared, that we get a server all to ourselves, with all of it's resources devoted only to our script?
Yep...
Quote:When your documentation says 4 CPU's, is that actually 4 CPU's, or just 1 CPU with 4 cores?
It is 4 CPU cores - they are XEON E5-2680 CPU's, so each physical CPU die has 8 cores - you get 4 of those. They support hyperthreading as well.
Quote:For instance, I am on a server with 2 CPU's but 8 cores, RAM is 8 GB, my space is 200GB on S4 SSD, and my host is telling me that what I have now in terms of available resources is "monstrous", compared to what Jamroom is offering for the same price.
Yeah if you have 16 Cores, 8G RAM and 200G Space then that is more than you're getting with our 4G server option.
Quote:What I don't understand, is if what he is saying is true, why we are not "smoking" the performance test? He says my limits are wide open, but the script is not utilizing the "monsterous" resources available to it. As if the installation is misconfigured, or not tuned properly to the server!
I've seen it break 1,000 twice, most tests are between 850-950, a few drop to the 300's always because of a temporarily high MSQL reading.
Honestly it all comes down to how the server is configured. The problem you are facing is that your server is completely tuned for the "lowest common denominator" - i.e. it is running Cpanel and needs to be able to support almost ANYTHING. There's a price to pay for that, and it is performance. You need A LOT more resources for Cpanel (WHM is a huge resource sink) as it has hundreds of different small servers running all the time checking for quotas, email spam, etc. It's also setup to run PHP in a multi-user environment so it has to run PHP as a CGI (as it as to be able to "setuid" to the user that it is running under) - this is the absolute SLOWEST way to run PHP - like 100 times slower than mod_php/RUID2, which is what we use on Jamroom Hosting.
It's a combination of a lot of things, but think of Cpanel hosting as a great big shopping mall with thousands of stores and an overwhelming number of things for you to do - there's a TON of overhead for all that. Jamroom Hosting is like a single store that JUST SELLS Jamroom - less overhead = better performance.
Let me know if that helps.
updated by @brian: 02/17/15 09:14:45AM
