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

Improve cost estimation/calculation if batch job was cancelled/failed #29

Open
zansinergise opened this issue Oct 13, 2023 · 1 comment

Comments

@zansinergise
Copy link
Collaborator

We should investigate how much costs were actually incurred if a batch job was cancelled or it failed during processing, since the costs/usage would probably be then lower than what we estimated before starting the job.

A bit more context: https://git.sinergise.com/team-6/openeo-sentinelhub-python-driver/-/merge_requests/318#note_583133

@zcernigoj
Copy link
Contributor

zcernigoj commented Oct 13, 2023

Cost of a failed tile inside a SH batch job is 0, for Sentinel Hub (platform itself).

Consequently

  • the cost of SH batch job where all tiles failed, is 0
  • the cost of SH batch job where some tiles failed, is lower

Can't find it in https://docs.sentinel-hub.com/api/latest/api/batch/
But can be checked for failed and partial SH batch jobs in SH dashboard for app_admin_openeo account.


On a separate note: we should determine, what the fixed (same for all jobs - failing or not) and variable (different for successful and failing jobs) costs are on AWS (lambda+dynamodb+s3) for the driver

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants