[jira] Commented: (TS-589) Add "tasks" threads and processor

["John Plevyak (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/TS-589?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12974394#action_12974394 ] 

John Plevyak commented on TS-589:
---------------------------------

Right now ET_CALL, ET_NET and ET_TASK are the same unless task_threads is set > 0

So, ET_DEFAULT_THREAD_TYPE could just be ET_TASK if you want and it would accomplish the
same thing.

> Add "tasks" threads and processor
> ---------------------------------
>
>                 Key: TS-589
>                 URL: https://issues.apache.org/jira/browse/TS-589
>             Project: Traffic Server
>          Issue Type: Improvement
>          Components: Core
>            Reporter: Leif Hedstrom
>            Assignee: Leif Hedstrom
>             Fix For: 2.1.5
>
>         Attachments: TS-589.diff
>
>
> Sometimes, in both the core and in SDK plugins, it might be useful to create "background tasks". Right now, it's only possible to schedule such tasks (continuations) on the normal net-threads. This could cause imbalance in thread "load", particularly for longer running tasks. A new thread type will be created, ET_TASK, which by default is the same as the net threads (ET_CALL), but via a records.config option, any continuations scheduled on ET_TASK can be off-loaded on a new set of threads (a threadpool with a configurable size).
> One new configuration option is added, with a default of 0:
> CONFIG proxy.config.task_threads INT 0
> In addition, more functionality can / should be added to the TasksProcessor, to make it easy and convenient to use. SDK APIs must also be added (or modified) to schedule plugin "tasks" on this thread pool.
> My initial checkin will be merely a "stub" processor, to get things started.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.