From owner-freebsd-questions@FreeBSD.ORG  Wed Mar 11 13:50:01 2015
Return-Path: <owner-freebsd-questions@FreeBSD.ORG>
Delivered-To: freebsd-questions@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id DE71FFD9
 for <freebsd-questions@freebsd.org>; Wed, 11 Mar 2015 13:50:01 +0000 (UTC)
Received: from mx01.qsc.de (mx01.qsc.de [213.148.129.14])
 (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id 96288E20
 for <freebsd-questions@freebsd.org>; Wed, 11 Mar 2015 13:50:01 +0000 (UTC)
Received: from r56.edvax.de (port-92-195-131-196.dynamic.qsc.de
 [92.195.131.196])
 (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by mx01.qsc.de (Postfix) with ESMTPS id 62F0A3CD9F;
 Wed, 11 Mar 2015 14:49:58 +0100 (CET)
Received: from r56.edvax.de (localhost [127.0.0.1])
 by r56.edvax.de (8.14.5/8.14.5) with SMTP id t2BDnwl7004935;
 Wed, 11 Mar 2015 14:49:58 +0100 (CET)
 (envelope-from freebsd@edvax.de)
Date: Wed, 11 Mar 2015 14:49:58 +0100
From: Polytropon <freebsd@edvax.de>
To: opendaddy@hushmail.com
Subject: Re: Limiting CPU on some processes on web server
Message-Id: <20150311144958.3ef9519d.freebsd@edvax.de>
In-Reply-To: <20150311134232.838ABC0451@smtp.hushmail.com>
References: <20150311122656.96F2020341@smtp.hushmail.com>
 <20150311141347.1013d42d.freebsd@edvax.de>
 <20150311134232.838ABC0451@smtp.hushmail.com>
Reply-To: Polytropon <freebsd@edvax.de>
Organization: EDVAX
X-Mailer: Sylpheed 3.1.1 (GTK+ 2.24.5; i386-portbld-freebsd8.2)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Cc: freebsd-questions@freebsd.org
X-BeenThere: freebsd-questions@freebsd.org
X-Mailman-Version: 2.1.18-1
Precedence: list
List-Id: User questions <freebsd-questions.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-questions>, 
 <mailto:freebsd-questions-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-questions/>
List-Post: <mailto:freebsd-questions@freebsd.org>
List-Help: <mailto:freebsd-questions-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-questions>, 
 <mailto:freebsd-questions-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 11 Mar 2015 13:50:02 -0000

On Wed, 11 Mar 2015 13:42:32 +0000, opendaddy@hushmail.com wrote:
> On 11. mars 2015 at 1:04 PM, "Polytropon" <freebsd@edvax.de> wrote:
> >
> >You can try ulimit. See "man sh" for ulimit parameters,
> >for example:
> >
> >             -t time
> >                     The maximal amount of CPU time to be used by 
> >each
> >                     process, in seconds.
> >
> >There are other restrictions you can apply, like memory
> >locking or simultaneous processes.
> >
> 
> Thanks, will give that a go.
> 
> Any idea how it compares to https://github.com/opsengine/cpulimit/ though?

The main differnce in functionality is that ulimit -t defines
the limit as time, whereas cpulimit defines it as percentage
of CPU resources used.

Another difference is that ulimit comes with FreeBSD's default
scripting shell, whereas cpulimit is a Linux program that has
to be compiled from source, after porting it, of course. :-)


-- 
Polytropon
Magdeburg, Germany
Happy FreeBSD user since 4.0
Andra moi ennepe, Mousa, ...