Skip to content

Conversation

@HansVRP
Copy link
Contributor

@HansVRP HansVRP commented Feb 19, 2025

No description provided.

@HansVRP HansVRP requested a review from soxofaan February 19, 2025 15:55
@HansVRP
Copy link
Contributor Author

HansVRP commented Feb 19, 2025

@soxofaan maybe good to rediscuss from this point (local unit tests are passing)

Copy link
Member

@soxofaan soxofaan left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

some quick notes

@soxofaan
Copy link
Member

soxofaan commented Feb 20, 2025

by the way, I don't think you had to create a new PR, you just could have continued on #730 by pushing to its feature branch (we now have three open PRs for this feature I think, which gets a bit messy)

@HansVRP HansVRP requested a review from soxofaan February 21, 2025 14:38
@HansVRP
Copy link
Contributor Author

HansVRP commented Feb 21, 2025

worked on your initial comments @soxofaan

currently checking why some unit tests are not passing

@soxofaan
Copy link
Member

@soxofaan I do not think the failing unit test in 3.11 are due to my changes?

indeed, that problem has been fixed on master by now

@HansVRP
Copy link
Contributor Author

HansVRP commented Feb 25, 2025

One issue I still see now and want to resolve is that currently launching jobs (to queue them for start) is still tied in to the backend load.

This means than when running at full capacity you will not already 'precreate jobs' which can instantly start running

@soxofaan
Copy link
Member

when running at full capacity you will not already 'precreate jobs' which can instantly start running

I'm not sure that pre-creating jobs instead of on the fly like we currently do will make that big of a difference as the time to create a job is usually negligible compared to the required time to start a job. Or do you experience different timings?

soxofaan added a commit that referenced this pull request Sep 9, 2025
is not necessary and eliminates `job_db.read()` which is not part of JobDatabaseInterface
soxofaan added a commit that referenced this pull request Sep 9, 2025
- make sure `persist` gets complete rows
- implement in both `FullDataFrameJobDatabase` and `STACAPIJobDatabase`

refs: #719, #736, #793
soxofaan added a commit that referenced this pull request Sep 9, 2025
soxofaan added a commit that referenced this pull request Sep 9, 2025
soxofaan added a commit that referenced this pull request Sep 9, 2025
refs #719, #441, #736

Explicitly add retry config for 429 response on POST request (e.g. start job)
soxofaan added a commit that referenced this pull request Sep 9, 2025
to improve signal/noise ratio of PR

(using darker and ruff)
soxofaan added a commit that referenced this pull request Sep 9, 2025
using `ruff format`, `ruff check --fix --select F401,I001` and `isort`
soxofaan added a commit that referenced this pull request Sep 9, 2025
- split `Task` hierarchy for better separation of concerns
- more tests for some basic classes
- clean up unused fixtures from tests
- DummyBackend: add setup_job_start_failure
soxofaan added a commit that referenced this pull request Sep 9, 2025
- support waiting directly in process_futures
- switch to DummyBackend
- use more dummy tasks TestJobManagerWorkerThreadPool to simplify setup
soxofaan added a commit that referenced this pull request Sep 9, 2025
soxofaan added a commit that referenced this pull request Sep 9, 2025
is not necessary and eliminates `job_db.read()` which is not part of JobDatabaseInterface
soxofaan added a commit that referenced this pull request Sep 9, 2025
- make sure `persist` gets complete rows
- implement in both `FullDataFrameJobDatabase` and `STACAPIJobDatabase`

refs: #719, #736, #793
soxofaan added a commit that referenced this pull request Sep 9, 2025
soxofaan added a commit that referenced this pull request Sep 9, 2025
soxofaan added a commit that referenced this pull request Sep 9, 2025
refs #719, #441, #736

Explicitly add retry config for 429 response on POST request (e.g. start job)
@soxofaan
Copy link
Member

soxofaan commented Sep 9, 2025

FYI: as this is a very long running PR with messy history, I tried to rebase the feature branch of this PR to clean it up a bit (e.g. commit squashing) to improve the signal-noise ratio and created PR #806 . The diff is practically identical to #736 (except for one empty line).

The discussion can stay here (#736), but #806 will be merged in the end

soxofaan added a commit that referenced this pull request Sep 9, 2025
to improve signal/noise ratio of PR

(using darker and ruff)
soxofaan added a commit that referenced this pull request Sep 9, 2025
using `ruff format`, `ruff check --fix --select F401,I001` and `isort`
soxofaan added a commit that referenced this pull request Sep 9, 2025
- split `Task` hierarchy for better separation of concerns
- more tests for some basic classes
- clean up unused fixtures from tests
- DummyBackend: add setup_job_start_failure
soxofaan added a commit that referenced this pull request Sep 9, 2025
- support waiting directly in process_futures
- switch to DummyBackend
- use more dummy tasks TestJobManagerWorkerThreadPool to simplify setup
soxofaan added a commit that referenced this pull request Sep 9, 2025
soxofaan added a commit that referenced this pull request Sep 9, 2025
is not necessary and eliminates `job_db.read()` which is not part of JobDatabaseInterface
soxofaan added a commit that referenced this pull request Sep 9, 2025
- make sure `persist` gets complete rows
- implement in both `FullDataFrameJobDatabase` and `STACAPIJobDatabase`

refs: #719, #736, #793
soxofaan added a commit that referenced this pull request Sep 9, 2025
soxofaan added a commit that referenced this pull request Sep 9, 2025
soxofaan added a commit that referenced this pull request Sep 9, 2025
refs #719, #441, #736

Explicitly add retry config for 429 response on POST request (e.g. start job)
@soxofaan
Copy link
Member

soxofaan commented Sep 9, 2025

ok, I decided to merge this (through PR #806) in 4171004 🥳

@soxofaan soxofaan closed this Sep 9, 2025
@soxofaan soxofaan deleted the hv_issue719-job-manager-threaded-job-start branch September 9, 2025 14:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

JobManager: create & start in parallel

3 participants