> Am 24.05.2020 um 23:24 schrieb Lonnie Abelbeck <li...@lonnie.abelbeck.com>:
> 
> 
> 
>> On May 24, 2020, at 3:49 PM, Michael Keuter <li...@mksolutions.info> wrote:
>> 
>> Try running the "yes" stresstest in the container, with the above 
>> limitations.
> 
> If I define lxc.cgroup.cpuset.cpus to 1, or 2 or 3, the "yes" stress-test [1] 
> only uses one core.
> 
> Setting lxc.cgroup.cpuset.cpus=4 the container does not start.
> 
> Not setting lxc.cgroup.cpuset.cpus all 4 cores are used.
> 
> Lonnie
> 
> [1]
> (start test)
> # for x in 1 2 3 4; do ( yes >/dev/null & ); done
> 
> (stop test)
> # killall yes

----
From the man page:

lxc-cgroup -n foo cpuset.cpus "0,3"
assign the processors 0 and 3 to the container.
----

I guess you define which CPU cores are allowed to use (0-3), that's why 4 does 
not work :-).

lxc.cgroup.cpuset.cpus=0,3  (maybe in quotes, should use core 1 and 4)

>>> Am 24.05.2020 um 22:35 schrieb Lonnie Abelbeck <li...@lonnie.abelbeck.com>:
>>> 
>>> I tried
>>> --
>>> lxc.cgroup.memory.limit_in_bytes = 512M
>>> lxc.cgroup.cpuset.cpus = 1
>>> --
>>> and 'htop' show 4 cores and 4 GB of RAM.
>>> 
>>> Kind of makes sense sense /proc/ is shared.
>>> 
>>> There is an optional lxcfs (uses FUSE) that offers a different /proc/ to 
>>> each container, but don't really think this is needed with AstLinux.
>>> 
>>> Lonnie
>> 
>> Try running the "yes" stresstest in the container, with the above 
>> limitations.
>> 
>>>> On May 24, 2020, at 3:25 PM, Michael Keuter <li...@mksolutions.info> wrote:
>>>> 
>>>> I did some tests and at least the number of cores worked for me. Look at 
>>>> these optional commands:
>>>> 
>>>> https://doc.astlinux.org/userdoc:guest_lxc_container#optional
>>>> 
>>>> The CPU shares are to set priorities between multiple containers. But it 
>>>> needs to be tested more.
>>>> 
>>>> 
>>>>> Am 24.05.2020 um 22:17 schrieb Lonnie Abelbeck 
>>>>> <li...@lonnie.abelbeck.com>:
>>>>> 
>>>>> Hi Michael,
>>>>> 
>>>>> Not currently.
>>>>> 
>>>>> For the AstLinux case we did not see much of an issue if the LXC can see 
>>>>> all cores and all RAM.
>>>>> 
>>>>> Lonnie
>>>>> 
>>>>> 
>>>>>> On May 24, 2020, at 3:12 PM, Michael Knill 
>>>>>> <michael.kn...@ipcsolutions.com.au> wrote:
>>>>>> 
>>>>>> Can you limit CPU resources to the  LXC container?
>>>>>> 
>>>>>> Regards
>>>>>> Michael Knill
>>>>>> 
>>>>>> On 24/5/20, 8:08 pm, "Michael Keuter" <li...@mksolutions.info> wrote:
>>>>>> 
>>>>>> 
>>>>>> 
>>>>>>> Am 24.05.2020 um 07:35 schrieb Michael Knill 
>>>>>>> <michael.kn...@ipcsolutions.com.au>:
>>>>>>> 
>>>>>>> Not really knowing anything about LXC Containers, just wondering if I 
>>>>>>> could install Centos and run QueueMetrics on the same box.
>>>>>>> This would be a pretty cool option!
>>>>>>> 
>>>>>>> https://www.queuemetrics.com/install-queuemetrics.jsp
>>>>>>> https://www.queuemetrics.com/blog/2018/12/04/dimensioning-queuemetrics/
>>>>>>> 
>>>>>>> Regards
>>>>>>> Michael Knill
>>>>>> 
>>>>>> Hi Michael,
>>>>>> 
>>>>>> in general this should work, but needs to be tested.
>>>>>> The question is how much diskspace, RAM and CPU power will be needed. 
>>>>>> All is shared with the host.
>>>>>> 
>>>>>> Michael
>>>> 
>>>> Michael

Michael

http://www.mksolutions.info





_______________________________________________
Astlinux-users mailing list
Astlinux-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/astlinux-users

Donations to support AstLinux are graciously accepted via PayPal to 
pay...@krisk.org.

Reply via email to