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

Tune raster-api config #54

Closed
2 of 4 tasks
anayeaye opened this issue Apr 28, 2022 · 3 comments
Closed
2 of 4 tasks

Tune raster-api config #54

anayeaye opened this issue Apr 28, 2022 · 3 comments

Comments

@anayeaye
Copy link
Collaborator

anayeaye commented Apr 28, 2022

What

The raster-api lambda is currently deployed with a large amount of debugging and some over-sized gdal settings. Right now the additional information and resources are useful for development--this ticket is a reminder to adjust the API configuration back down when the backend is in an operational state.

AC

  • - Debug settings removed (CPL_DEBUG, CPL_CURL_VERBOSE)
  • - VSI_CACHE_SIZE and CPL_VSIL_CURL_CHUNK_SIZE tuned for current usage patterns
  • - Timeout and memory size tuned for current usage patterns
  • - Explain or remove GDAL_HTTP_RETRY_DELAY override
@aboydnw
Copy link

aboydnw commented Jul 24, 2022

@anayeaye is the backend in an operational state now? or will that happen after deployed to MCP?

@anayeaye
Copy link
Collaborator Author

@aboydnw we have removed some of the slower debugging settings but have not officially embarked on performance tuning for the raster API which I think we decided against for this PI. However, I think if we take a quick pass on the timeout and memory settings--maybe next sprint?--we could probably just close this ticket knowing that we will be working on performance tuning in the next PI.

@aboydnw
Copy link

aboydnw commented Sep 7, 2022

Closing for now, will reopen or open a new ticket if any additional performance tuning is needed

@aboydnw aboydnw closed this as completed Sep 7, 2022
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