Assess performance and configuration limits of dissolution jobs
- Dominant language
- JavaScript
- Stars
- 23
- Forks
- 62
- Avg merge
- 24m
- Merged PRs (30d)
- 1
Description
Right now in legacy it's capped at 2000 per week and it was determined it's too risky to try and increase (due to the processing capabilities and how long it takes to send all the messages)
Tasks : Create and execute a test plan to evaluate the performance and limitations of the company dissolution job.
Goals:
- To determine how many companies can be successfully dissolved per week
- Identify and record any technical or system caps (e.g. batch size limits, processing timeouts, etc.)
- Assess how job execution parameters can be optimized for better performance.
Contributor guide
No contributing guide indexed for this repository
Research direction
No files, tests, or entry points are named. Start by locating the company dissolution job and its execution configuration, then review the existing 2,000-per-week limit and how processing and message delivery are measured. Done means a documented test plan and results showing sustainable weekly capacity, technical caps, and recommended parameter adjustments.
Written by the indexing model from the issue text.
Assessment
- Domain
- backend, performance
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100