Just to note I see that in triton the cpu_cap is set as well as cpu_shares == max_physical_memory
I am struggling to understand how this works. I am guessing that if the ratio of cpu_cap to cores is low then its not that noticeable to the guests, the threads get through in a reasonable amount of time but with the E7-x cpu's that have high core counts and the ratio is higher this will become a more serious problem especially for multithreaded apps ? Thanks Len On 2 December 2016 at 09:44, Len Weincier <l...@cloudafrica.net> wrote: > This is the classic symptom of a machine with a cpu_cap less than its CPU >> (core) count. >> > > So the vm sees all the cores and dispatches threads / processes for that > many cores but the actual uasage is limited by the cpu_cap so the threads > are stalling waiting for the OS to give them a slot to run hence the load > avg climbing iiuc. Setting cpu_cap=0 sets the machine free and its > responsive > > Whats the right way to share the cores for LX brand machines then seeing > as we cant limit the access to the cores ? In triton is see the default > packages set the cpu_cap as well which would result in the same issue ? > > I have had a look at https://wiki.smartos.org/display/DOC/CPU+Caps+and+ > Shares and am not sure what todo ? > > Thanks > Len > > ------------------------------------------- smartos-discuss Archives: https://www.listbox.com/member/archive/184463/=now RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00 Modify Your Subscription: https://www.listbox.com/member/?member_id=25769125&id_secret=25769125-7688e9fb Powered by Listbox: http://www.listbox.com
