kestra-io / kestra-io/plugin-scripts

Add in-memory capacity for TaskRunner Process and Docker

Open
#437 0 comments 0 reactions 0 assignees View on GitHub
area/backend area/plugin good first issue kind/performance
Dominant language
Java
Stars
19
Forks
33
Avg merge
2d 12h
Merged PRs (30d)
9

Description

### Feature description

Today, we moved the "/tmp/kestra-wd" folder to a tmpfs to take advantage of in-memory performance. Would it be possible to also offer this capability to runners (Process and Docker at least) to benefit from these same advantages?
Example:
```
type: io.kestra.plugin.scripts.shell.Script
taskRunner:
type: io.kestra.plugin.scripts.runner.docker.Docker / type: io.kestra.plugin.core.runner.Process
pullPolicy: IF_NOT_PRESENT
cpu:
cpus: 1
memory:
memory: 512Mi
volume:
inMemory: true
limit: 8G
```

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by inspecting the existing tmpfs handling for the "/tmp/kestra-wd" folder and the Process and Docker task runners. Determine how the example `volume.inMemory` and `volume.limit` settings should apply to both runners, then verify that each runner supports the requested in-memory capacity configuration.

Written by the indexing model from the issue text.

Assessment

Tech stack
docker, java
Domain
devops
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.