-
Notifications
You must be signed in to change notification settings - Fork 4
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
worldcover extract requires too much memory #99
Comments
Note that I fixed a similar issue for sentinel-2, where I avoided expensive tileToLayout by setting a 'predefinedExtent' when creating BandCompositeRasterSource. |
@EmileSonneveld based on what we saw yesterday, with the mask rasterization going OOM, I committed one fix to really ensure that the spatial partitioner is used. |
It seems like some issue where Scala does not behave like expected. Maybe there is already a warning for this during compilation. I'll check. |
Current state is in screenshot below:
|
Just tried running it again: stage 10 is now much better. |
Last improvement did not yet solve the issue, we're still stuck with a resampling that we don't want to happen in the first place:
|
…sources should be pre-aligned to layout
…the incoming extent, reduces special cases
* apply global_bounds also when not in utm projection * do not apply rounding to resolution as a general rule, stick to globalbounds which is assumed to be rounded already if needed * also skip resampling for layers that are not utm, all raster sources should be pre-aligned to layout * align extent to layout before loading data * further apply principle of always aligning raster sources to the incoming extent, reduces special cases * update agera5 and dem tests, output has improved thanks to changes
The issue with stage 14 in previous screenshot is entirely gone. |
…vider." This reverts commit 5e93010.
Stage 15 went from one hour to 5 minutes by changing partitioner settings. |
I had to set memory very high for this one:
This stage is the problem:
flatMap at FileLayerProvider.scala:758
Thread dumps mostly seem to be stuck in tileToLayout.
Worldcover products are quite large (36000, 36000), and have a block size of 1024x1024.
The text was updated successfully, but these errors were encountered: