I've been using the default (which if I read correctly is 5s?); seems
likely that a good answer here for me would be to push it out to
$something_long and use restart.txt or somesuch to uptake changes. I may
try that this week.

My MaxRequests was already 10k. I'm guessing that 5 seconds of cache was
approximately equivalent to jack and squat. I'm not sure if my attempt to
tune by granting more workers would've done me any good.


On Fri, May 23, 2014 at 5:25 PM, Chuck <cssc...@gmail.com> wrote:

> I had it set to 3 minutes for this test.
>
> I am going to work on trying some different settings.
>
> So far the best result has been with the following settings
>
> PassengerMaxRequests 5000
> environment_timeout 15 minutes
> "service httpd graceful" whenever my svn update script detects a change.
>
> I will be working on getting more information.
>
>
>
>
> On Friday, May 23, 2014 3:24:43 PM UTC-5, Josh Partlow wrote:
>>
>> Hi Tristan, Chuck,
>>
>> What environment_timeout do you have set currently?
>>
>> On Friday, May 23, 2014 12:20:33 PM UTC-7, Tristan Smith wrote:
>>>
>>> Whuf.   I'm already at 10000, so that's not it for me.
>>>
>>> Seems like the doubled run time was just murdering me in the face.
>>> Trying to run 1000 clients in 30m was just too much. Guess I could make it
>>> an hour splay, but the overall resource requirement change is sufficiently
>>> large I'm probably just going to see about opting out of directory
>>> environments for a couple revisions, wait for them to tune up a bit.
>>>
>>>
>>>
>>>
>>> On Fri, May 23, 2014 at 10:23 AM, Chuck <css...@gmail.com> wrote:
>>>
>>>> I am noticing increase CPU and Memory requirements from Puppet 3.4.3
>>>>
>>>> I had to set the following passenger config so that my server would not
>>>> run out of memory:
>>>> PassengerMaxRequets 10000
>>>>
>>>> CPU idle 3.4.3 = 70% - 80%
>>>> Memory utilization = 52%
>>>>
>>>> CPU idle 3.6.1 =  60% - 73%
>>>> Memory utilization = 85%
>>>>
>>>> --
>>>> You received this message because you are subscribed to a topic in the
>>>> Google Groups "Puppet Users" group.
>>>> To unsubscribe from this topic, visit https://groups.google.com/d/
>>>> topic/puppet-users/arLckU-mPhw/unsubscribe.
>>>> To unsubscribe from this group and all its topics, send an email to
>>>> puppet-users...@googlegroups.com.
>>>> To view this discussion on the web visit https://groups.google.com/d/
>>>> msgid/puppet-users/2c9172e1-6129-46d1-94f1-38c078d72226%
>>>> 40googlegroups.com<https://groups.google.com/d/msgid/puppet-users/2c9172e1-6129-46d1-94f1-38c078d72226%40googlegroups.com?utm_medium=email&utm_source=footer>
>>>> .
>>>>
>>>> For more options, visit https://groups.google.com/d/optout.
>>>>
>>>
>>>  --
> You received this message because you are subscribed to a topic in the
> Google Groups "Puppet Users" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/puppet-users/arLckU-mPhw/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> puppet-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/puppet-users/490ad0ec-a35a-4ab3-a0a9-88e52e752083%40googlegroups.com<https://groups.google.com/d/msgid/puppet-users/490ad0ec-a35a-4ab3-a0a9-88e52e752083%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
>
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CAKdO7cc%2BYe1-LSSk5_DBrMdD5YaqCdcRwuGKL6VqJ3AwGNE4Zg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to