4:28 a.m.
Hello,
minimal requirements for memory is now higher with introduction of
Foreman integration. Example machine:
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+
16635 elastics 20 0 1452m 218m 9772 S 1.3 11.9 0:16.01
16428 tomcat 20 0 2103m 194m 9940 S 1.0 10.6 0:12.84
16824 katello 20 0 304m 176m 3260 S 0.0 9.6 0:10.44
16818 katello 20 0 304m 176m 3264 S 0.0 9.6 0:10.37
16924 katello 20 0 301m 171m 1580 S 0.0 9.3 0:00.58
16925 katello 20 0 301m 167m 536 S 0.0 9.2 0:00.02
16719 foreman 20 0 249m 127m 3052 S 0.0 7.0 0:05.92
16723 foreman 20 0 249m 127m 2968 S 0.0 6.9 0:05.74
16544 apache 20 0 942m 43m 5976 S 0.3 2.4 0:01.67
8774 root 20 0 862m 16m 2816 S 0.0 0.9 0:09.59
16562 mongodb 20 0 837m 14m 1840 S 0.3 0.8 0:00.61
16590 qpidd 20 0 308m 10m 3780 S 0.0 0.6 0:00.12
Please ignore the VIRT column asi it shows files mapped into the memory
and since Java applications maps JAR files, that is the reason why we
see 3.5 gigs of memory used by Java. Let's focus on the RES (resident)
memory column:
As you can see, typical memory consumption of the nightly instance is
cca 1.4 GB for: Katello (2 thins 1 job workoer) , Candlepin, Foreman (2
thins) and ElasticSerch. Then we need to add some memory for httpd
(Pulp), mongodb, qpidd, postgresql and also system.
I think the 2 GB minimal requirement has been reached, I recommend to
use 2.5 GB as an absolute minimum (expect some swapping) and 3 GB as the
recommended minimal value. For production setups, I would see 6 GB as a
good value to start with.
--
Later,
Lukas "lzap" Zapletal
#katello #systemengine
8:30 a.m.
On Tue 18 Dec 2012 03:28:06 AM MST, Lukas Zapletal wrote:
Hello,
minimal requirements for memory is now higher with introduction of
Foreman integration. Example machine:
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+
16635 elastics 20 0 1452m 218m 9772 S 1.3 11.9 0:16.01
16428 tomcat 20 0 2103m 194m 9940 S 1.0 10.6 0:12.84
16824 katello 20 0 304m 176m 3260 S 0.0 9.6 0:10.44
16818 katello 20 0 304m 176m 3264 S 0.0 9.6 0:10.37
16924 katello 20 0 301m 171m 1580 S 0.0 9.3 0:00.58
16925 katello 20 0 301m 167m 536 S 0.0 9.2 0:00.02
16719 foreman 20 0 249m 127m 3052 S 0.0 7.0 0:05.92
16723 foreman 20 0 249m 127m 2968 S 0.0 6.9 0:05.74
16544 apache 20 0 942m 43m 5976 S 0.3 2.4 0:01.67
8774 root 20 0 862m 16m 2816 S 0.0 0.9 0:09.59
16562 mongodb 20 0 837m 14m 1840 S 0.3 0.8 0:00.61
16590 qpidd 20 0 308m 10m 3780 S 0.0 0.6 0:00.12
Please ignore the VIRT column asi it shows files mapped into the memory
and since Java applications maps JAR files, that is the reason why we
see 3.5 gigs of memory used by Java. Let's focus on the RES (resident)
memory column:
As you can see, typical memory consumption of the nightly instance is
cca 1.4 GB for: Katello (2 thins 1 job workoer) , Candlepin, Foreman (2
thins) and ElasticSerch. Then we need to add some memory for httpd
(Pulp), mongodb, qpidd, postgresql and also system.
I think the 2 GB minimal requirement has been reached, I recommend to
use 2.5 GB as an absolute minimum (expect some swapping) and 3 GB as the
recommended minimal value. For production setups, I would see 6 GB as a
good value to start with.
Lana - is a bug on the docs required for this?
--
Jason E. Rist
Senior Software Engineer
Systems Management and Cloud Enablement
Red Hat, Inc.
+1.919.754.4048
Freenode: jrist
github/identi.ca: knowncitizen
10:41 a.m.
On 12/18/2012 11:28 AM, Lukas Zapletal wrote:
I think the 2 GB minimal requirement has been reached, I recommend
to
use 2.5 GB as an absolute minimum (expect some swapping) and 3 GB as the
recommended minimal value. For production setups, I would see 6 GB as a
good value to start with.
1) I used Katello with 2 GB without problem - just testing not too much
data, but that is what I call minimal
2) if you check:
https://access.redhat.com/knowledge/docs/en-US/CloudForms/1.1/html/Instal...
You will notice of:
At least 4GB and ideally 8GB of memory for each instance of CloudForms
Cloud Engine and CloudForms System Engine. It is also recommended to use
swap space where possible.
--
Miroslav Suchy
Red Hat Systems Management Engineering
9:30 a.m.
On Tue, Dec 18, 2012 at 05:41:28PM +0100, Miroslav Suchy wrote:
On 12/18/2012 11:28 AM, Lukas Zapletal wrote:
>I think the 2 GB minimal requirement has been reached, I recommend to
>use 2.5 GB as an absolute minimum (expect some swapping) and 3 GB as the
>recommended minimal value. For production setups, I would see 6 GB as a
>good value to start with.
1) I used Katello with 2 GB without problem - just testing not too
much data, but that is what I call minimal
But it must be swapping... and it's unresponsive.
2) if you check:
https://access.redhat.com/knowledge/docs/en-US/CloudForms/1.1/html/Instal...
You will notice of:
At least 4GB and ideally 8GB of memory for each instance of
I know, but if you check our project wiki page:
https://fedorahosted.org/katello/wiki/Install
Minimum amount of memory is 1.8 GB and swap must be enabled with at
least 2 GB.
I think we should change this to:
2.5 GB mem, "sufficient" amount of swap.
Opinions?
--
Later,
Lukas "lzap" Zapletal
#katello #systemengine
12:26 p.m.
On 19.12.2012 16:30, Lukas Zapletal wrote:
> > 1) I used Katello with 2 GB without problem - just testing
not too
> > much data, but that is what I call minimal
> >
But it must be swapping... and it's unresponsive.
I'm not sure if it was swapping, there was plenty of swap.
And it was fairly responsive. I did not measure, but it was much much
faster then Katello in development mode.
When Fedora say that its minimal requirements are intel 586, then it
autocratically doesn't mean that people will run it on 586.
I will add to that wiki as recommended setup: 8 GB RAM.
This way people will know that if they have less 8 GB then performance
of Katello will be suboptimal. Do you concur?
Mirek
3:36 a.m.
I edited the page.
LZ
On Wed, Dec 19, 2012 at 07:26:46PM +0100, Miroslav Suchy wrote:
On 19.12.2012 16:30, Lukas Zapletal wrote:
>>> 1) I used Katello with 2 GB without problem - just testing not too
>>> much data, but that is what I call minimal
>>>
>But it must be swapping... and it's unresponsive.
I'm not sure if it was swapping, there was plenty of swap.
And it was fairly responsive. I did not measure, but it was much
much faster then Katello in development mode.
When Fedora say that its minimal requirements are intel 586, then it
autocratically doesn't mean that people will run it on 586.
I will add to that wiki as recommended setup: 8 GB RAM.
This way people will know that if they have less 8 GB then
performance of Katello will be suboptimal. Do you concur?
Mirek
_______________________________________________
katello mailing list
katello(a)lists.fedorahosted.org
https://lists.fedorahosted.org/mailman/listinfo/katello
--
Later,
Lukas "lzap" Zapletal
#katello #systemengine
9:08 a.m.
+1
On 12/20/2012 01:36 AM, Lukas Zapletal wrote:
I edited the page.
LZ
On Wed, Dec 19, 2012 at 07:26:46PM +0100, Miroslav Suchy wrote:
> On 19.12.2012 16:30, Lukas Zapletal wrote:
>>>> 1) I used Katello with 2 GB without problem - just testing not too
>>>> much data, but that is what I call minimal
>>>>
>> But it must be swapping... and it's unresponsive.
>
> I'm not sure if it was swapping, there was plenty of swap.
>
> And it was fairly responsive. I did not measure, but it was much
> much faster then Katello in development mode.
>
> When Fedora say that its minimal requirements are intel 586, then it
> autocratically doesn't mean that people will run it on 586.
>
> I will add to that wiki as recommended setup: 8 GB RAM.
>
> This way people will know that if they have less 8 GB then
> performance of Katello will be suboptimal. Do you concur?
>
> Mirek
> _______________________________________________
> katello mailing list
> katello(a)lists.fedorahosted.org
> https://lists.fedorahosted.org/mailman/listinfo/katello
--
Mike McCune
mmccune AT redhat.com
Red Hat Engineering | Portland, OR
Systems Management | 650-254-4248
4149
days inactive
4151
days old
katello@lists.fedorahosted.org
6 comments
4 participants
participants (4)
-
Jason Rist -
Lukas Zapletal -
Mike McCune -
Miroslav Suchý