There has been no need for a reboot for quite some time now. About the new settings, while I\'m not 100% sure I guess that you still ned to specify 2 cores for 200% and 4 cores for 400%. It would however make sense to no longer need to specify the numer of cores as 200% is obviously 2 cores isn\'t it ? If not then why would someone specify for instance 3 cores for 200% ?

I appreciate the response, but with respect I\'d rather hear something conclusive instead of speculation on your part. I\'m a firm believer in not making any assumptions and there\'s certainly no harm in seeking verification if in doubt

The reason I asked these questions was to get a definitive response rather than guesswork. The documentation has, over the years, been a tad confusing and sometimes lacking. An example of this is http://docs.cloudlinux.com/limits.html which still references CPU % instead of the new \"speed\" value. Another big example is the historical confusion over the number of CPU\'s vs the percentage of CPU power, with the former overriding the latter or taking precedence in certain situations. Not as intuitive as you would expect, but still something graspable. Since they have effectively replaced the previous \"percentage of CPU power\" variable with the new \"speed\" variable, it stands to reason that the nCPU *could* still maintain this same behaviour. Since this isn\'t mentioned in the documentation or changelog I would just like to seek clarification on this. I agree, there is no reason to specify certain combinations of settings, but again - no harm in seeking clarification.

In regards to the reboot being required, this setting was previously marked with an asterisk in the LVE manager stating that a reboot was required if changed, but now does not. This is, at least in my mind, no official confirmation that this is no longer required so I would also like confirmation of this. Please bear in mind not all users update their Kernels regularly and reboot to take advantage of newer changes.

Can any CL staff please confirm the above? Thanks.

No speculation, I'm sure about not needing to reboot and am also sure about 200% needing 2 cores.

I also asked if it couldn't be calculated automaticaly and if not why, so lets wait for CloudLinux's answer now :)

The new speed value just translates into % when you save it's just a helper so you don't need to calculate the percentage manually.

For the reboot it was necessary with the first versions only.  I remember the asterisk but that must be at least a year ago, before cagefs became stable unless I'm mistaken.

And this is why I asked for CloudLinux to comment, to avoid situations like this ;)

I think we have our wires crossed somewhere and perhaps you've misinterpreted what I'm asking. I wasn't asking if 200% "speed" needs 2 cores on the machine, which is how you seem to have interpreted it. I was asking if the nCPU setting is required if the speed setting is set. If nCPU is set, will it take precedence over "% of CPU" as it used to before they replaced this setting with "speed"?

As simply as possible - If, for example, "speed" is set to 200% and "nCPU" is set to "2", which one (if any) takes priority? Of course, if you set "speed" to 200% and "nCPU" to "4", naturally both can't be valid at the same time so surely one has to take effect. This is what I'm trying to establish here. CloudLinux will happily accept seemingly conflicting values, so this is something that needs to be clarified.

With the previous limits, the documentation says the following:

"The smallest of the two is used to define how much CPU power will be accessible to the customer."

The new documentation says nothing of the sort.

Clearer now? :)

With regards to the reboot, this was visible in LVE manager not THAT long ago and definitely wasn't only a first few revision thing.

I would love a clarification also. thanks.

Sorry about this. I had understood that the only thing that had changed was the unit for 1%. However the documentation now says that ncpu is no longer required. Lets wait for cloudlinux to confirm about this. As if this is the case then why wasn\'t the ncpu setting removed ?

More info regarding speed is here: http://docs.cloudlinux.com/index.html?cpu_limits.html
Basically speed lets you set CPU limit relative to a single core, or as a number of hrz.

Hello Igor,

According to the documentation the ncpu setting is no longer used. Can you please confirm that if I set 300% and 1 in ncpu it will use 3 CPU\'s ?

If you use CPU + NCPU --> it would work as before
If you use --speed --> NCPU ignored, not used.

In the lve cpanel interface 6 % and 2 cpu\'s was converted to 197% and 2 cpu\'s. Should\'nt the 2 cpu\'s setting be empty ? Does the cpanel interface use speed and ignore the ncpu setting ? Or did it increase all my accounts settings ?

@Richard: "According to the documentation the ncpu setting is no longer used." unless we're reading completely different documentation, you are wrong. It states nothing of the sort. Please stop making this statement because you will confuse other people as you've done multiple times in this thread already.

@Igor;  "If you use CPU + NCPU --> it would work as before 
If you use --speed --> NCPU ignored, not used."

Can you guys please, please, PLEASE just take some time to craft an actually comprehensible response and then update your documentation? With your above response, what are you actually saying? "If you use CPU + NCPU --> it would work as before." is what you are really saying here that if you haven't upgraded, nothing will change? Isn't that already a little obvious?

"If you use --speed --> NCPU ignored, not used." - great. So the next logical question is, why does the nCPU option remain?

Can you please try and work with your clients here and provide some detailed documentation that makes sense of the situation? I'm disappointed I had to come to the forum to seek clarification of something that should've been simple enough to explain in your documentation. I'm also very disappointed that with all the posts we have made, you didn't address them properly and instead just gave short brief responses.

The documentation for the command line version is clear. LVE Manager documentation does need to be updated.

Although I did not understand Igor\'s answer the first time I read it (missed the ignored part), it now makes sense, actually says everything and allows us to understand that the ncpu setting will likely be removed in a future release of LVE Manager as Igor said it\'s currently ignored.

Thanks Igor, keep up the good work

@Richard: Are you purposefully being obtuse?? I've mentioned LVE manager several times in this thread, and in fact my very first line in the very first post says the following:

With the recent changes to CloudLinux and LVE manager....

To add to this, the "CPU limits" page of the documentation, which is the page you would expect to find detailed documentation on the implementation and settings regardless of command-line or UI interface, does not mention anything about nCPU being discontinued or no longer being used. Your comments about it being mentioned in the command line documentation are therefore irrelevant and unhelpful. For my own amusement I looked at the documentation for lvectl (which you claim confirms it is redundant and not being used) and it, also, does not mention anything about nCPU being redundant.

Although I did not understand Igor's answer the first time I read it (missed the ignored part), it now makes sense, actually says everything and allows us to understand that the ncpu setting will likely be removed in a future release of LVE Manager as Igor said it's currently ignored.

You continue to make assumptions, false interpretations and attempts to "read between the lines" in the documentation and Igor's responses. This may work for you and your business, but for me and ours I would like concrete and definitive responses here. I don't think that's unreasonable in the slightest. If CloudLinux are going to update their software, they need to update the documentation too. How they expect anyone to understand how their software works and to manage things properly without up to date and accurate documentation is beyond me.

I would really appreciate it if you would stop posting your assumptions and interpretations here. You are just going to confuse people looking for genuine and official information on the subject matter.

The new version was only released a couple of days ago, give them a bit of time and they will update the documentation

Richard, please stop posting.

As i had the same doubts, i contacted Support asking them to explain me a little more how is working now.


Here is the first response: 

Hello.
True, NCPU abolished in the new versions. 
1 core = 100%, 2 = 200% core, core 4 = 400%, etc. 
For example, 1 core = 2000MHz. If I set a value of 150% - that account can consume 3000MHz.

For setting limits in the new versions use the CPU-parameter. 

I understand that the option of SPEED (% or Mhz) it's the mandatory, so the nCPU should be ignored... but, to make sure, i asked that:

Me: 
So if i set 400 at CPU %, it's full 4 Cores.

Even if i set at nCPU 1?, should i just ignore nCPU?

Thanks

Support:
Hello, Jose.

> So if i set 400 at CPU %, it's full 4 Cores.
Yes.

> Even if i set at nCPU 1?, should i just ignore nCPU?
Yes, this option will be ignored.

Hope this helps a little on this topic.

Have a good day

@Jose: Thanks for the information

I didn\'t want to create a support ticket as I thought the information would be useful for others here in public. Shame they are able to provide the information in the ticket but not in their own documentation or here on the forums. Disappointing.

Several years since installing cloudlinux and I still feel like I am a beta tester...

First of all, on ALL of our cpanel servers upcp got hung up after the latest lve-stats upd ate. I had to manuall kill upcp and do a /scripts/upcp --force afterwards.

This is where upcp hung..


[20140723.024207]      [538983] Dependency Installed:
[20140723.024207]      [538983]   alt-sqlite.x86_64 0:3.8.3.1-1.el5                                             
[20140723.024207]      [538983] 
[20140723.024207]      [538983] Updated:
[20140723.024207]      [538983]   lve-stats.noarch 0:0.10-31.1.el5                                              
[20140723.024207]      [538983] 
[20140723.024207]      [538983] Complete!
[20140723.024213]      [538983] checkyum version 21.1


ANYWAY ..now that I finally got that going again. I look at the WHM lve limits and it's just random numbers such as "13" for the cpu limit and I can't change the bloody thing! Trying to edit the default settings says "settings saved" but when I goto the main page it still shows "13" as the cpu limit. WTF? How did it come up with that number to begin with?

OK ANYWAY ... so I thought maybe it's just the WHM frontend that's buggy so I login to root shell and use the "lvectl" command.

lvectl limits all shows this..


[~]# lvectl limits all
      ID   SPEED    NCPU    VMEM      EP      IO
 default     104       1    1.0G      20      25
     514     104       1    1.0G      20      25
     643     104       1    1.0G      20      25
.
.. and so on, same for every user.

104 WHAT ????? 104% of cpu ? 104 Mhz ?? WHAT IS IT DOING!!!!

Trying to rese t this limit with this command:

lvectl apply all --speed=25% 

does NOTHING. "lvectl limits all" stil shows that "104" as 'SPEED' as WHM still shows "13"

What the hell is going on here? I feel like I have completely lost control over the server as cloudlinux is just putting arbitrary and non-consistent limits in the cli/whm and is not accepting the new ones like "lvectl apply all --speed=25% "

THIS IS NOT GOOD ENOUGH!!! We can't run buggy software that actually has such a huge and visible impact on our servers!

Come on Igor this is not good enough and you know it. You need to test this crap thoroughly before releasing it. We are paying customers and right now I am paying for nothing but stress.
PS> The documentation is and always has been a joke. It is written in such a way that only the person who wrote it could ever understand it.

I am really getting fed up with this. We had a customer make a simple mistake writing a PHP script with an endless loop in it and it crashed the server by exhausing all ram and swap in 2 minutes. I am starting to wonder if we're paying for snake oil.

Really really angry right now.

I am sorry for being MIA. A lot of things required my attention in the past few weeks (and that will continue for 3-4 more weeks I am afraid), and as the result I let documentation & communication via social media to lag behind. I will try to be more responsive.
Jules -- you were right at being angree with me -- I should have paid it more attention.
Delta - I am sorry to hear about upcp being stuck -- next time you see something like that - do ps -auxw, and save the output for us so we can trace it. I haven't heard other users having that problem. Sounds strange.

SPEED vs CPU limits. Documentation had been updated to explain SPEED works. http://docs.cloudlinux.com/index.html?limits.html
It overrides both CPU & NCPU options -- and the only option that matters.
LVE Manager will be updated to remove NCPU within next few weeks.
lve-stats will be updated in the next 2-3 months -- as we are working on a very big rework, that should add many cool featurs (like snapshoting of processes & queries when limits are hit, burstable limits and reseller limits).

If anyone has any more questions regarding speed & CPU -- I would be happy to answer them.

Hi Bogdan

as it turns out the package "lvemanager" was not installed on any of my cpanel boxes so I must have been using an old WHM frontend for Lve manager ... the new one looks completely different (much nicer).

edit: fixed unrelated problem removed comments regarding it.

In regards to the "104" - it makes no sense. All the servers are 4 core (8 threads). The WHM frontend now shows SPEED as "100" which is what I want if I understood your docs correctly (ie. I want each user to be able to use max 1 core). However "lvectl list" still shows every user's SPEED set to "104"
I've even run

lvectl set default --speed=100% 
lvectl apply all 

and when I do lvectl list its still showing "104" in the SPEED column. is this just a problem with lvectl ?

Here is my output for rpm -qa | grep -i lve (can you tell me if I have all the packages and if they are correct versions please??)


[~]# rpm -qa | grep -i lve
kernel-2.6.18-408.8.2.el5.lve0.8.61.3
lve-1.2-1.12.el5.cloudlinux
kernel-2.6.18-448.16.1.el5.lve0.8.70
liblve-devel-1.2-1.12.el5.cloudlinux
lve-wrappers-0.6-1.el5.cloudlinux
lve-utils-1.4-18.3.el5.cloudlinux
kernel-headers-2.6.18-471.3.1.el5.lve0.8.72
liblve-1.2-1.12.el5.cloudlinux
pam_lve-0.3-7.el5.cloudlinux
lvemanager-0.8-1.32.el5.cloudlinux
kmod-lve-2.6.18-408.8.2.el5.lve1.1.65.3-1.1-9.9.el5
lve-stats-0.10-31.2.el5

I even did yum reinstall lve-utils but it didn't make any change - "list" still shows that 104 number... so random.