Skip to content

We should add github actions and tests to benchmark computational cost of the ETL as well #2

@mmcdermott

Description

@mmcdermott

This would ensure that users know how much it costs to run a given ETL for any subsequent derived ETL repositories. The benchmarking can follow what is done for NRTs, here: https://mmcdermott.github.io/nested_ragged_tensors/dev/bench/

Metadata

Metadata

Assignees

No one assigned

    Labels

    Computational EfficiencyRelating to the computational efficiency of the ETL (or of derived ETLs)

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions