Skip to content

Hourly aggregation uses too much memory #162

@mhidas

Description

@mhidas

When aggregating larger datasets, the hourly averaging codes (velocity and non-velocity) can run out of memory and fail.
In general it seems the process can easily eat up 4-5Gb of memory (and want more...)

Metadata

Metadata

Assignees

No one assigned

    Labels

    hourly_timeseriesIssues relating to the hourly time series productvelocity_hourlyIssues relating to the velocity hourly time series product

    Type

    No type

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions