Hi list
We are having some issues with our pulp server and it's memory usage.
As you can see in the attached image, we upgraded the server from 8 to 12 gigs
a couple of weeks back but it still eats up all the available memory.
Since memory is full most of the time it started swapping.
$ free
On 04/07/2015 06:13 AM, Roth, Sandro wrote:
Hi list
We are having some issues with our pulp server and it's memory usage.
As you can see in the attached image, we upgraded the server from 8 to 12
gigs a couple of weeks back but it still eats up all the available memory.
Since memory is
(nectar.downloaders.threaded).
Sandro
-Original Message-
From: pulp-list-boun...@redhat.com [mailto:pulp-list-boun...@redhat.com] On
Behalf Of Randy Barlow
Sent: Dienstag, 7. April 2015 16:12
To: pulp-list@redhat.com
Subject: Re: [Pulp-list] Memory Usage
-BEGIN PGP SIGNED MESSAGE
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hello Sandro,
MongoDB might be using the extra RAM. MongoDB uses memory mapped
files[0] for its indices and collections. As a result, it will
generally use all the RAM it can get. I suggest deploying MongoDB on a
separate system (or VM) from the
Barlow
Sent: Dienstag, 7. April 2015 16:12 To: pulp-list@redhat.com
Subject: Re: [Pulp-list] Memory Usage
Hello Sandro,
MongoDB might be using the extra RAM. MongoDB uses memory mapped
files[0] for its indices and collections. As a result, it will
generally use all the RAM it can get. I
