[systemd-devel] RFC: Setting TasksMax= by default

Reindl Harald h.reindl at thelounge.net
Fri Nov 13 07:06:44 PST 2015

Am 13.11.2015 um 15:27 schrieb Zbigniew Jędrzejewski-Szmek:
> On Fri, Nov 13, 2015 at 02:49:39PM +0100, Lennart Poettering wrote:
>> Heya!
>> b) I'd like to introduce DefaultTasksMax= that controls the default
>>     value of the per-unit TasksMax= by default, and would like it to
>>     set to some value such 1024 out-of-the-box. This will mean that any
>>     service or scope created will by default be limited to 1024
>>     tasks. This of course is a change from before that has the
>>     potential to break some daemons that maintain an excessive number
>>     of processes or threads. However, I think it's a much better choice
>>     to raise the limit for them, rather than stay unlimited for all
>>     services by default. I think 1024 is not particularly low, but also
>>     not particularly high. Note that the kernel by default limits the
>>     number of processes to 32K in total anyway.
> Shouldn't it be lower than 1024? For services which have many tasks,
> 1024 will not be enough, but for 99.9% of services it will be two
> orders of magnitude too many. I guess we can start with those
> settings, and the controller turned on, and then maybe readjust based
> on real-world usage

1024 is OK, below or main webserver which is capable running that many 
preforkers and has this configuration for at least 2 years now

<IfModule prefork.c>
  StartServers            30
  MinSpareServers         30
  MaxSpareServers         60
  ServerLimit           1024
  MaxClients             800
  ListenBacklog         2000
  MaxRequestsPerChild    500

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 181 bytes
Desc: OpenPGP digital signature
URL: <http://lists.freedesktop.org/archives/systemd-devel/attachments/20151113/b4972aed/attachment.sig>

More information about the systemd-devel mailing list