Search: streamed_task_maximum

…are then injected to the queue front and processed as soon as possible. You can get more information about task priorities in Task prioritization section of REST API documentation and in Understanding SPE processing priority article. server.task_default_priority # Task default priority. Priority must be number from to 99. This priority will be set # to each task if request doesn’t…

…workers are not shown): non-colored pending tasks are waiting in the queue (task state in the response to GET /pending/{ID} request says “waiting“) colored pending tasks are being handled by processing workers (task state in the response to GET /pending/{ID} request says “running“) SPE is configured with 3 standard and 2 realtime workers, i.e. 5 tasks are handled simultaneously (one…

…Realtime workers must be set separately to enable RTP or HTTP stream processing. Principally, it is the same as setting normal workers: server.n_realtime_workers = The SPE maintains its own queue of task requests waiting to be processed and the following directive determines the allowed number of tasks in the queue. You can do fine-tuning for each SPE instance load and…

…enabled in SPE configuration file (enabled by default, see server.task_priorities_enable option) and default priority value set the prioritize role enabled for SPE user creating the processing task If prioritization is enabled and processing task is started by a user without the “prioritize” role, task is started with default priority. Task priority is defined by a number from (highest priority) to…

…the maximum number of simultaneously running tasks. # Multithread settings server.n_workers = 8 server.n_realtime_workers = 8 Requests for additional file processing tasks are put in a queue and processed according their order and priorities. Requests for additional stream processing tasks are refused with HTTP status 403 (the realtime nature of stream processing does not allow any queuing). File processing can…

…name and password (obviously 😉) whether the account is active or not – accounts may be turned off and on user role – any combination of user – allowed to use all SPE functionality, except for the /admin/… endpoints admin – allowed to use all SPE functionality, including the /admin/… endpoints prioritize – allowed to prioritize SPE tasks, see Task…