Currently WorkflowRun.waitForCompletion spins on a thread just so it can hold a (flyweight) Executor open. Similarly, ExecutorStepExecution.PlaceholderTask spins just to hold a (heavyweight) Executor open. These are wasteful. There should be an optional Task or Executable interface that can run asynchronously, without literally consuming a native Thread for each one.
- depends on
-
JENKINS-34450 Deadlock between Executor and AsynchronousExecution
-
- Open
-
- is blocking
-
JENKINS-28182 Revisit use of $JENKINS_SERVER_COOKIE and Launcher.kill
-
- Resolved
-
- is duplicated by
-
JENKINS-26098 Asynch Queue.Executable
-
- Resolved
-
- is related to
-
JENKINS-22941 Way to mark an Executable that should not block isReadyToRestart
-
- Resolved
-
-
JENKINS-26900 Hide flyweight master executor when ≥1 heavyweight executors running as subtasks
-
- Resolved
-
- links to
[JENKINS-25938] Lock an Executor without creating a Thread
Link |
New:
This issue is duplicated by |
Link |
New:
This issue is related to |
Link |
New:
This issue is related to |
Assignee | New: Jesse Glick [ jglick ] |
Status | Original: Open [ 1 ] | New: In Progress [ 3 ] |
Remote Link | New: This issue links to "PR 1610 (Web Link)" [ 12169 ] |
Resolution | New: Fixed [ 1 ] | |
Status | Original: In Progress [ 3 ] | New: Resolved [ 5 ] |
Labels | Original: api executor performance threads workflow | New: api executor lts-candidate performance threads workflow |
Link |
New:
This issue is blocking |
Labels | Original: api executor lts-candidate performance threads workflow | New: api executor performance threads workflow |