any limitation in program process ?

[haiyuanhe]

I use the latest supervisor release in

version: 2008ServerR2 6.1.7601 SP1 Multiprocessor Free

and I startup the python daemon with supervisor. found that the daemon print log so slow and nothing response(will block) too.

I check anything else in the daemon , when I start then python daemon without supervisor everything is work. but use supervisor would be slow .

Have you anything idea about this problem ? Anything limit in mulitprocess ?

BTW the python daemon use mulitprocess lib with python

[alexsilva]

The supervisor has a processing limiter. This limit is set by the delaysecs Try setting a value smaller than default 0.2s

For example:

[supervisord]
delaysecs=0.005

However this will increase the use of cpu by the supervisor.

It is also possible to configure affinity and priorities of processes.

But the priority and affinity options want the supervisor to be started by an administrator.

[haiyuanhe]

it doesn't work . still delay to print log and no reponse

[supervisor]
delaysecs=0.005

[program: xxx]
cpupriority=high
cpuaffinity=7

[haiyuanhe]

I want to reproduce the problem with sample code . Write a lot of logs in second , if the log delay print . Can we prove the supervisor have throttle or limit the program in some where ?

[alexsilva]

The supervisor just runs the program with the subprocess module and reads stdout / stderr.

Important points highlighted below: process.execute StreamAsync