Skip to content

Track memory usage in tests #19

@macournoyer

Description

@macournoyer

How do we make sure that:

  • there are no memory leaks in our code
  • everything that needs to be GCed by Ruby has been
  • we don't use Ruby objects that have been GCed (GC.stress=trye could do the trick, but is slow, see https://github.com/Shopify/liquid-wasm/issues/168. It could be an option we turn on in CI?).

I think we could leverage #18, and measure memory usage during the execution. After a warmup phase, memory usage should be stable.

Maybe we could also measure allocations like in SFR.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions