On Sat, Mar 20, 2010 at 3:05 PM, Lucas Meneghel Rodrigues <[email protected]>wrote:
> On Tue, Mar 9, 2010 at 5:51 PM, Martin Bligh <[email protected]> wrote: > > On Tue, Mar 9, 2010 at 12:44 PM, Gregory Smith <[email protected]> wrote: > >> Raise the ulimit that the scheduler runs under. Some of the autoserv > >> processes it launches more ram (for brief periods of time) due to large > >> external processes they launch. > > > > Two questions: > > > > 1. Should this just be done for the child autoservs? > > 2. What are the large processes? If they're only your internal ones, then > > this would be better done in a site-specific override, or as a global > config > > option? > The large processes were some internal tools we needed to call that are unfortunately wrappers for things written in java with the jvm configured to demand 1gb of ram up front (despite not actually using that much for this program). raising the ulimit was the easiest solution for us. I really don't care about the ulimit. fwiw, its a good practice to run things within a resource limit that sufficient to keep them from thrashing your entire server if they run amok but that limit will be different for everyone. That is why we put the prior rather arbitrary ulimit in place in the first place. Its a failsafe mechanism. > This being a shell script, it is harder to extract values from the > global config file (to a point it's not worth picking up values from > the file). A site specific override would be OK, but need to verify > first if this is not beneficial to upstream. > > I just took the time and read the script, it makes use of > log_daemon_msg, which is a utility commonly present in debian boxes, I > guess we should make an effort to make this a bit more distro > agnostic... > Yeah we're running on ubuntu. if someone wants to make a multi-distro init script or multiple init scripts for different distros, be my guest. what we have today works for us so we can't really complain. > > >> Signed-off-by: Gregory Smith <[email protected]> > >> > >> --- autotest/utils/autotest.init 2010-03-09 12:26:49.000000000 > -0800 > >> +++ autotest/utils/autotest.init 2010-03-09 12:26:49.000000000 > -0800 > >> @@ -31,7 +31,7 @@ > >> ## END GOOGLE > >> > >> log_daemon_msg "Starting monitor_db_babysitter" > >> - ( ulimit -v 819200 ; \ > >> + ( ulimit -v 2048000 ; \ > >> start-stop-daemon --start --quiet --chuid $BECOME_USER \ > >> --background --exec $BASE_DIR/scheduler/monitor_db_babysitter ) > >> } > >> _______________________________________________ > >> Autotest mailing list > >> [email protected] > >> http://test.kernel.org/cgi-bin/mailman/listinfo/autotest > >> > > _______________________________________________ > > Autotest mailing list > > [email protected] > > http://test.kernel.org/cgi-bin/mailman/listinfo/autotest > > > > > > -- > Lucas >
_______________________________________________ Autotest mailing list [email protected] http://test.kernel.org/cgi-bin/mailman/listinfo/autotest
