stackabletech / stackabletech/superset-operator
Superset Example loading slow - can we set requests/limits for load job?
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 35
- Forks
- 4
- Avg merge
- 12h 20m
- Merged PRs (30d)
- 10
Description
The loading of the Superset examples by the setup Job is slow. I found that the python process running the import job seems to be the bottleneck. However, we can't give it more resources, because there's no way for us to configure that from the outside.
In fact, we don't even request any resources at all! We should probably request something minimal.
Maybe we could re-use the limits etc. from superset itself?
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the setup Job definition and the existing Superset resource requests and limits. Compare how those values are configured and determine whether the load Job can reuse them or needs minimal defaults. Done means the import Job has configurable resource requests and limits, with its behavior covered by the relevant tests if they exist.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kubernetes, python
- Domain
- infrastructure
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100