Open mmcfarland opened 7 years ago
Free memory graphed for the particular worker instance that reported the error. Not correlated with number of model executions happening, but from the consistent pattern, it's possible that each spike is a single execution - which would be a substantial allocation. Caring about intermediate raster data types may be an important optimization. The good news is that nothing appears to hold onto memory for long and that it does not leak.
Staging has reported a memory error for the following request, however the AoI size is small, indicating that the memory was not consumed by this single request, but that this was the one which pushed over the limit. It occurs at the focal operation. Would be interesting to correlate some resource metrics with an execution.
Stack trace
Model input
https://rollbar.com/ProjectICP/Bee-Pollinator/items/2/