MISP / MISP/misp-cloud

NICE the workers?

Open
#24 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Shell
Stars
74
Forks
18
PR merge metrics
No merged PRs in 30d

Description

I really appreciate the current build.

Question: Is there a way to nice the workers? Running in AWS on a tiny instance the workers tend to kill the responsiveness.

Happy to receive a workaround.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

The issue mentions workers running on AWS and asks whether they can be niced, but it does not identify a file, entry point, or test. First determine how workers are launched and where their process priority could be configured; done means documenting or implementing a workable approach that preserves responsiveness on a small instance.

Written by the indexing model from the issue text.

Assessment

Tech stack
aws, shell
Domain
cloud
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.