Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[FR]: Pre-processor optimization #1485

Open
jleaniz opened this issue May 30, 2024 · 0 comments
Open

[FR]: Pre-processor optimization #1485

jleaniz opened this issue May 30, 2024 · 0 comments
Labels
enhancement Needs triage New issues that need triage

Comments

@jleaniz
Copy link
Collaborator

jleaniz commented May 30, 2024

What is the feature you are proposing?

Evidence pre-processing runs every time a new job is executed. For some types of jobs, this is not necessary. As an example, a CompressedDirectory evidence would only need to be decompressed once for subsequent jobs to run. Currently, the pre-processor runs every single time.

What would this feature improve or what problem would it solve?

Task performance would be better, especially for larger, compressed evidence types.

What alternatives have you considered?

No response

@jleaniz jleaniz added enhancement Needs triage New issues that need triage labels May 30, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement Needs triage New issues that need triage
Projects
None yet
Development

No branches or pull requests

1 participant