Just to add to this.
The issue is happening in an LX zone.
SmartOS image is 20160915T211220Z
Thanks
Len
On 1 December 2016 at 18:17, Len Weincier wrote:
> Hi all
>
> Is there any issues with these cpu's and smartos - "Intel(R) Xeon(R) CPU
> E7-4850 v4 @ 2.10GHz" ?
>
> We
Hello Len,
How many threads or processes is the workload generating? Joyent and LX
zones see all cpus and memory of the host (regardless of cpu_cap setting as
far I know) so your workload may have gone overboard when it seen the 32*4
CPU threads and 1.5TB of RAM. In particular, is the workload
A regression regarding ZFS property reporting was found after the
release last week. The fix has been backported with a release respin
placed in Manta:
/Joyent_Dev/public/SmartOS/20161129T003638Z
https://us-east.manta.joyent.com/Joyent_Dev/public/SmartOS/smartos.html#20161129T003638Z
On 24
On 12/ 2/16 05:17 AM, Len Weincier wrote:
Hi all
Is there any issues with these cpu's and smartos - "Intel(R) Xeon(R)
CPU E7-4850 v4 @ 2.10GHz" ?
We have a new host with 4 of those cpus and 1.5TB ram and moved some
machines to the host which are now thrashing the cpu - load avg in a
test
Hi all
Is there any issues with these cpu's and smartos - "Intel(R) Xeon(R) CPU
E7-4850 v4 @ 2.10GHz" ?
We have a new host with 4 of those cpus and 1.5TB ram and moved some
machines to the host which are now thrashing the cpu - load avg in a test zone
with cpu_cap=800 is over 180 and just
To expand on Nigel’s excellent point, I’d suggest browsing through Intel and
Facebook’s (independent, I think) research on scaling Memcached threads:
https://software.intel.com/en-us/articles/enhancing-the-scalability-of-memcached-0
>
> 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