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

Proposal: Enable Optional Parallelism in PyGeoProcessing #377

Open
phargogh opened this issue Mar 5, 2024 · 1 comment
Open

Proposal: Enable Optional Parallelism in PyGeoProcessing #377

phargogh opened this issue Mar 5, 2024 · 1 comment
Labels
proposal Proposals requiring team feedback

Comments

@phargogh
Copy link
Member

phargogh commented Mar 5, 2024

This is a proposal to enable optional concurrent.futures.Executor-based parallelism in pygeoprocessing functions that are likely to be CPU-bound. Details are in this google doc:

https://docs.google.com/document/d/124-k3EFMozO2x20Fo0rI3_XOPxXucG18_RVEXFdsAfg/edit

@phargogh phargogh added the proposal Proposals requiring team feedback label Mar 5, 2024
@phargogh
Copy link
Member Author

phargogh commented Mar 5, 2024

We talked about this in the software team meeting 2024-03-05 and had a few suggestions come up as we iterate on this proposal:

  • Add some example scripts demonstrating the various use cases
    • To better understand the tradeoffs in API decisions, for align_and_resize_raster_stack in particular, elaborate on the case of breaking out warp_raster calls to separate taskgraph tasks compared with the proposed approach
  • Describe where documentation would be added to describe the new features of this proposed functionality

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

No branches or pull requests

1 participant