On Wed, Jan 11, 2012 at 02:09, Antonio Xanxess
antonio.sanchez.agui...@gmail.com wrote:
Ramin and Gabriel Thanks for the answer and feel the delay in
replying.
Solve the problem of abusive use of memory by modifying some
parameters of passenger, shortening the lifetime of instances of
Hello everyone,
Ramin and Gabriel Thanks for the answer and feel the delay in
replying.
Solve the problem of abusive use of memory by modifying some
parameters of passenger, shortening the lifetime of instances of
puppetmaster and performing a triple nodes dispersion: Dispersion time
(the nodes
Hello everyone,
Trevor and Jeffrey Thanks for the information but I have included
puppet task cron dispersed, what I want is to optimize the service as
much as possible and discharged the RAM since I have yet to get around
more than 2000 nodes.
I included in the message above two questions I'd
Hello,
On 11-12-21 08:01 AM, Antonio Xanxess wrote:
MinSpareThreads 25
MaxSpareThreads 75
MaxRequestsPerChild 0
How much RAM does each Apache process take? Does Apache take more and
more memory up to the point you mentioned (11Gb taken)?
With luck, if you set
Apache or any other http server is usually not the problem in a
Passenger based Puppet master because it's only peripherally involved
in the actual work. Here's roughly how a client receives a catalog.
Client runs, makes a connections to Apache on the Puppet master
Puppet master Apache receives,
Hi Brice,
Thanks for the reply. I've been looking at what you sent me and now I
think I meet all these requirements.
Currently, each node accesses the settings every hour, which means
that from 1927 to 1960 = 32 nodes checking every minute.
I use Passenger with apache, maybe it's the best
