Hi, I'm surprised to see pulp_resource_manager using that much memory. The memory required for the workers varies greatly depending on the job currently being executed. For a system that is only running workers I would expect that 4 GB of memory should be sufficient. Mongo is going to use all of available memory on a machine for it's cache so if you are trying to limit the memory used then it should be run in it's own VM. Regards,
-Barnaby ----- Original Message ----- From: "Sean Waite" <[email protected]> To: [email protected] Sent: Monday, June 22, 2015 8:46:04 AM Subject: [Pulp-list] Children resource usage Hi, I've got a pulp server running, and I'd like to add some children. The server itself is a bit hard up on resources, so we're going to rebuild with a larger one. How much resources would the children use? Is it a fairly beefy process/memory hog? We've got a large number of repositories. pulp-resource-manager seems to be using 1.7G of memory, with a .7G of mongodb. Any pointers on how much I might be able to expect? Thanks -- Sean Waite [email protected] Cloud Operations Engineer GPG 3071E870 TraceLink, Inc. Be Excellent to Each Other _______________________________________________ Pulp-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/pulp-list _______________________________________________ Pulp-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/pulp-list
