Fwd: Re: lxc-performance?

Fwd: Re: lxc-performance?

[MALATTAR]

-------- Message original --------
Sujet: 	Re: lxc-performance
Date : 	Thu, 07 Oct 2010 16:56:05 +0200
De : 	MALATTAR <mouhannad.alattar-jI/kxupzh7HSLaPbPq81kw@public.gmane.org>
Pour : 	MALATTAR <mouhannad.alattar-jI/kxupzh7HSLaPbPq81kw@public.gmane.org>



Le 07/10/2010 16:43, MALATTAR a écrit :
> ------------------------------------------------------------------------
> 06.10.2010 23:41, MALATTAR ?????:
>
> >/  the container dora1, where i launch an instance of my IDS, does not take
> />/  more than 70 MB as memory even though the memory limit for it is much
> />/  bigger than this value,
> /
> How do you measure memory usage?

by using the command:
lxc-cgroup -n dora1 memory.usage_in_bytes
>   What's in memory.max_usage_in_bytes of
> the container's cgroup?
executing the next command lxc-cgroup -n dora1 memory.max_usage_in_bytes
gave me 70193152 bytes

> -- 
> Mouhannad AlATTAR
> Doctorant à L'UFR Sciences,Techniques et Gestion de l'Industrie
> Pôle multimedia de Franche Comté - numerica
> 1, cours Leprince-Ringuet
> 25201 Montbéliard
> Fixe bureau : 03 81 99 47 87
> Portable : 06 16 71 05 10
>
>


-- 
Mouhannad AlATTAR
Doctorant à L'UFR Sciences,Techniques et Gestion de l'Industrie
Pôle multimedia de Franche Comté - numerica
1, cours Leprince-Ringuet
25201 Montbéliard
Fixe bureau : 03 81 99 47 87
Portable : 06 16 71 05 10

Re: Fwd: Re: lxc-performance?

[Serge E. Hallyn]

Quoting MALATTAR (mouhannad.alattar-jI/kxupzh7HSLaPbPq81kw@public.gmane.org):
> 
> 
> -------- Message original --------
> Sujet: 	Re: lxc-performance
> Date : 	Thu, 07 Oct 2010 16:56:05 +0200
> De : 	MALATTAR <mouhannad.alattar-jI/kxupzh7HSLaPbPq81kw@public.gmane.org>
> Pour : 	MALATTAR <mouhannad.alattar-jI/kxupzh7HSLaPbPq81kw@public.gmane.org>
> 
> 
> 
> Le 07/10/2010 16:43, MALATTAR a écrit :
> > ------------------------------------------------------------------------
> > 06.10.2010 23:41, MALATTAR ?????:
> >
> > >/  the container dora1, where i launch an instance of my IDS, does not take
> > />/  more than 70 MB as memory even though the memory limit for it is much
> > />/  bigger than this value,
> > /
> > How do you measure memory usage?
> 
> by using the command:
> lxc-cgroup -n dora1 memory.usage_in_bytes
> >   What's in memory.max_usage_in_bytes of
> > the container's cgroup?
> executing the next command lxc-cgroup -n dora1 memory.max_usage_in_bytes
> gave me 70193152 bytes

Interesting - that's not the value you set in your intro email.

What does /var/lib/lxc/dora1/config have?

Re: Fwd: Re: lxc-performance?

[MALATTAR]

  Le 08/10/2010 18:41, Serge E. Hallyn a écrit :
> Quoting MALATTAR (mouhannad.alattar-jI/kxupzh7HSLaPbPq81kw@public.gmane.org):
>>
>> -------- Message original --------
>> Sujet: 	Re: lxc-performance
>> Date : 	Thu, 07 Oct 2010 16:56:05 +0200
>> De : 	MALATTAR<mouhannad.alattar-jI/kxupzh7HSLaPbPq81kw@public.gmane.org>
>> Pour : 	MALATTAR<mouhannad.alattar-jI/kxupzh7HSLaPbPq81kw@public.gmane.org>
>>
>>
>>
>> Le 07/10/2010 16:43, MALATTAR a écrit :
>>> ------------------------------------------------------------------------
>>> 06.10.2010 23:41, MALATTAR ?????:
>>>
>>>> /  the container dora1, where i launch an instance of my IDS, does not take
>>> />/  more than 70 MB as memory even though the memory limit for it is much
>>> />/  bigger than this value,
>>> /
>>> How do you measure memory usage?
>> by using the command:
>> lxc-cgroup -n dora1 memory.usage_in_bytes
>>>    What's in memory.max_usage_in_bytes of
>>> the container's cgroup?
>> executing the next command lxc-cgroup -n dora1 memory.max_usage_in_bytes
>> gave me 70193152 bytes
> Interesting - that's not the value you set in your intro email.
???
> What does /var/lib/lxc/dora1/config have?
>
lxc.utsname = dora1
lxc.tty = 4
lxc.network.type = veth
lxc.network.flags = up
lxc.network.link = br-node1
lxc.network.name = eth0
lxc.network.mtu = 1500
lxc.network.ipv4 = 10.0.0.1/24
lxc.network.hwaddr = 12:DA:00:4B:54:45
lxc.rootfs = /lxc/rootfs.fedora
lxc.mount = /lxc/fstab.fedora
lxc.cgroup.devices.deny = a
# /dev/null and zero
lxc.cgroup.devices.allow = c 1:3 rwm
lxc.cgroup.devices.allow = c 1:5 rwm
# consoles
lxc.cgroup.devices.allow = c 5:1 rwm
lxc.cgroup.devices.allow = c 5:0 rwm
lxc.cgroup.devices.allow = c 4:0 rwm
lxc.cgroup.devices.allow = c 4:1 rwm
# /dev/{,u}random
lxc.cgroup.devices.allow = c 1:9 rwm
lxc.cgroup.devices.allow = c 1:8 rwm
# /dev/pts/* - pts namespaces are "coming soon"
lxc.cgroup.devices.allow = c 136:* rwm
lxc.cgroup.devices.allow = c 5:2 rwm
# rtc
lxc.cgroup.devices.allow = c 254:0 rwm
lxc.cgroup.memory.limit_in_bytes = 1524435456
lxc.pts=1


-- 
Mouhannad AlATTAR
Doctorant à L’UFR Sciences,Techniques et Gestion de l’Industrie
Pôle multimedia de Franche Comté - numerica
1, cours Leprince-Ringuet
25201 Montbéliard
Fixe bureau : 03 81 99 47 87
Portable : 06 16 71 05 10

Re: Fwd: Re: lxc-performance?

[KAMEZAWA Hiroyuki]

On Fri, 08 Oct 2010 10:09:51 +0200
MALATTAR <mouhannad.alattar@univ-fcomte.fr> wrote:

> Le 07/10/2010 16:43, MALATTAR a écrit :
> > ------------------------------------------------------------------------
> > 06.10.2010 23:41, MALATTAR ?????:
> >
> > >/  the container dora1, where i launch an instance of my IDS, does not take
> > />/  more than 70 MB as memory even though the memory limit for it is much
> > />/  bigger than this value,
> > /
> > How do you measure memory usage?
> 
> by using the command:
> lxc-cgroup -n dora1 memory.usage_in_bytes
> >   What's in memory.max_usage_in_bytes of
> > the container's cgroup?
> executing the next command lxc-cgroup -n dora1 memory.max_usage_in_bytes
> gave me 70193152 bytes
> 

Hmm. what latencytop shows ?

You can see this kind of output.
==
Cause                                                Maximum     Percentage
Writing a page to disk                            551.6 msec         36.8 %
Fork() system call                                273.7 msec          1.1 %
Page fault                                        253.9 msec         29.5 %
Writing buffer to disk (synchronous)              225.9 msec          2.9 %
Creating block layer request                      202.7 msec         17.1 %
Walking directory tree                            161.5 msec          1.4 %
[congestion_wait]                                  97.6 msec          4.4 %
Executing a program                                97.1 msec          0.3 %
synchronous write                                  73.9 msec          0.1 %
==

IMHO, if memory limit is the problem, "Page Fault" tend to be big. 


Thanks,
-Kame

_______________________________________________
Containers mailing list
Containers@lists.linux-foundation.org
https://lists.linux-foundation.org/mailman/listinfo/containers

Re: Fwd: Re: lxc-performance?

[MALATTAR]

  Le 12/10/2010 07:05, KAMEZAWA Hiroyuki a écrit :
> On Fri, 08 Oct 2010 10:09:51 +0200
> MALATTAR<mouhannad.alattar@univ-fcomte.fr>  wrote:
>
>> Le 07/10/2010 16:43, MALATTAR a écrit :
>>> ------------------------------------------------------------------------
>>> 06.10.2010 23:41, MALATTAR ?????:
>>>
>>>> /  the container dora1, where i launch an instance of my IDS, does not take
>>> />/  more than 70 MB as memory even though the memory limit for it is much
>>> />/  bigger than this value,
>>> /
>>> How do you measure memory usage?
>> by using the command:
>> lxc-cgroup -n dora1 memory.usage_in_bytes
>>>    What's in memory.max_usage_in_bytes of
>>> the container's cgroup?
>> executing the next command lxc-cgroup -n dora1 memory.max_usage_in_bytes
>> gave me 70193152 bytes
>>
> Hmm. what latencytop shows ?
>
> You can see this kind of output.
> ==
> Cause                                                Maximum     Percentage
> Writing a page to disk                            551.6 msec         36.8 %
> Fork() system call                                273.7 msec          1.1 %
> Page fault                                        253.9 msec         29.5 %
> Writing buffer to disk (synchronous)              225.9 msec          2.9 %
> Creating block layer request                      202.7 msec         17.1 %
> Walking directory tree                            161.5 msec          1.4 %
> [congestion_wait]                                  97.6 msec          4.4 %
> Executing a program                                97.1 msec          0.3 %
> synchronous write                                  73.9 msec          0.1 %
> ==
>
> IMHO, if memory limit is the problem, "Page Fault" tend to be big.
>
>
> Thanks,
> -Kame
>
>
executing latencytop during the execution of my program gave me:
Cause                                                                    
Maximum     Percentage
fsync() on a file (type 'F' for details)                      45.1 
msec       2.2 %
Waiting for event (poll)                                          5.0 
msec         47.9 %
Userspace lock contention                                    5.0 
msec         43.1 %
Waiting for event (select)                                      4.8 
msec          5.7 %
Throttling GPU while waiting for commands         3.4 msec          0.4 %
[i915_do_wait_request]                                         3.3 
msec          0.5 %
Waiting for data on unix socket                             0.3 
msec          0.1 %
Waiting for TTY data                                              0.2 
msec          0.1 %

Process mysqld (291)                               Total:   2.3 msec
Waiting for data on unix socket                     0.3 msec        100.0 %

It seems that there is no problem...

also memtest command was able to allocate up to 1024MB but it takes a 
long time
for one loop only ...
So, i think the problem is in my program not in the container, is not it?

a+

-- 
Mouhannad AlATTAR
Doctorant à L’UFR Sciences,Techniques et Gestion de l’Industrie
Pôle multimedia de Franche Comté - numerica
1, cours Leprince-Ringuet
25201 Montbéliard
Fixe bureau : 03 81 99 47 87
Portable : 06 16 71 05 10



_______________________________________________
Containers mailing list
Containers@lists.linux-foundation.org
https://lists.linux-foundation.org/mailman/listinfo/containers

Re: Fwd: Re: lxc-performance?

[Balbir Singh]

On Thu, Oct 14, 2010 at 7:11 PM, MALATTAR
<mouhannad.alattar-jI/kxupzh7HSLaPbPq81kw@public.gmane.org> wrote:
>
>  Le 12/10/2010 07:05, KAMEZAWA Hiroyuki a écrit :
> > On Fri, 08 Oct 2010 10:09:51 +0200
> > MALATTAR<mouhannad.alattar-jI/kxupzh7HSLaPbPq81kw@public.gmane.org>  wrote:
> >
> >> Le 07/10/2010 16:43, MALATTAR a écrit :
> >>> ------------------------------------------------------------------------
> >>> 06.10.2010 23:41, MALATTAR ?????:
> >>>
> >>>> /  the container dora1, where i launch an instance of my IDS, does not take
> >>> />/  more than 70 MB as memory even though the memory limit for it is much
> >>> />/  bigger than this value,
> >>> /
> >>> How do you measure memory usage?
> >> by using the command:
> >> lxc-cgroup -n dora1 memory.usage_in_bytes
> >>>    What's in memory.max_usage_in_bytes of
> >>> the container's cgroup?
> >> executing the next command lxc-cgroup -n dora1 memory.max_usage_in_bytes
> >> gave me 70193152 bytes
> >>
> > Hmm. what latencytop shows ?
> >
> > You can see this kind of output.
> > ==
> > Cause                                                Maximum     Percentage
> > Writing a page to disk                            551.6 msec         36.8 %
> > Fork() system call                                273.7 msec          1.1 %
> > Page fault                                        253.9 msec         29.5 %
> > Writing buffer to disk (synchronous)              225.9 msec          2.9 %
> > Creating block layer request                      202.7 msec         17.1 %
> > Walking directory tree                            161.5 msec          1.4 %
> > [congestion_wait]                                  97.6 msec          4.4 %
> > Executing a program                                97.1 msec          0.3 %
> > synchronous write                                  73.9 msec          0.1 %
> > ==
> >
> > IMHO, if memory limit is the problem, "Page Fault" tend to be big.
> >
> >
> > Thanks,
> > -Kame
> >
> >
> executing latencytop during the execution of my program gave me:
> Cause
> Maximum     Percentage
> fsync() on a file (type 'F' for details)                      45.1
> msec       2.2 %
> Waiting for event (poll)                                          5.0
> msec         47.9 %
> Userspace lock contention                                    5.0
> msec         43.1 %
> Waiting for event (select)                                      4.8
> msec          5.7 %
> Throttling GPU while waiting for commands         3.4 msec          0.4 %
> [i915_do_wait_request]                                         3.3
> msec          0.5 %
> Waiting for data on unix socket                             0.3
> msec          0.1 %
> Waiting for TTY data                                              0.2
> msec          0.1 %
>
> Process mysqld (291)                               Total:   2.3 msec
> Waiting for data on unix socket                     0.3 msec        100.0 %
>
> It seems that there is no problem...
>
> also memtest command was able to allocate up to 1024MB but it takes a
> long time
> for one loop only ...
> So, i think the problem is in my program not in the container, is not it?

Could you please dump your cgroup filesystem? What is
memory.limit_in_bytes, memory.stat? fysnc() can clearly hold up things
across the filesystem with ext3 and other FS. The source does sound
like mysql database for the frequent fsync's - is that correct? What
does the iotop output look like?

Balbir

Re: Fwd: Re: lxc-performance?

[Pavel Labushev]

14.10.2010 21:41, MALATTAR пишет:

> also memtest command was able to allocate up to 1024MB but it takes a
> long time
> for one loop only ...

OK, the problem is not with LXC memory limits therefore.

> So, i think the problem is in my program not in the container, is not it?

It could be your program or too low rlimits. What 'ulimit -a' says? Note
that rlimits are per-process, so you should investigate their values
from inside your program's operating environment.

_______________________________________________
Containers mailing list
Containers@lists.linux-foundation.org
https://lists.linux-foundation.org/mailman/listinfo/containers

Re: Fwd: Re: lxc-performance?

[Serge E. Hallyn]

Quoting MALATTAR (mouhannad.alattar-jI/kxupzh7HSLaPbPq81kw@public.gmane.org):
> 
> 
> -------- Message original --------
> Sujet: 	Re: lxc-performance
> Date : 	Thu, 07 Oct 2010 16:56:05 +0200
> De : 	MALATTAR <mouhannad.alattar-jI/kxupzh7HSLaPbPq81kw@public.gmane.org>
> Pour : 	MALATTAR <mouhannad.alattar-jI/kxupzh7HSLaPbPq81kw@public.gmane.org>
> 
> 
> 
> Le 07/10/2010 16:43, MALATTAR a écrit :
> > ------------------------------------------------------------------------
> > 06.10.2010 23:41, MALATTAR ?????:
> >
> > >/  the container dora1, where i launch an instance of my IDS, does not take
> > />/  more than 70 MB as memory even though the memory limit for it is much
> > />/  bigger than this value,
> > /
> > How do you measure memory usage?
> 
> by using the command:
> lxc-cgroup -n dora1 memory.usage_in_bytes
> >   What's in memory.max_usage_in_bytes of
> > the container's cgroup?
> executing the next command lxc-cgroup -n dora1 memory.max_usage_in_bytes
> gave me 70193152 bytes

Ah, linux/Documentation/cgroups/memory.txt explains that max_usage_in_bytes
reports the maximum memory usage recorded, not the limit.  Look at
	lxc-cgroup -n dora1 memory.max_usage_in_bytes

-serge