Skip to content
This repository has been archived by the owner on Aug 17, 2022. It is now read-only.

Performance tracing #267

Open
ayazhafiz opened this issue Sep 29, 2020 · 0 comments
Open

Performance tracing #267

ayazhafiz opened this issue Sep 29, 2020 · 0 comments
Labels
a:bin a:lib c:test e:2 Takes effort help wanted Extra attention is needed
Milestone

Comments

@ayazhafiz
Copy link
Collaborator

I am thinking of adding performance/efficiency tracing to the library.

Basically the idea is to have a set of scripts that run on every CI build and
log data about how long a set of executions took and how much memory was
consumed.

The important thing here is to make sure that the input we are checking is
future-proof and will have a large variance on system resources. So I am
thinking we run over a subset of test files, in determinstic order, in serial.

It might be too early to add this for it to be very useful. But that's okay; its
better to have it early and it not be useful than to add it later and miss a lot
of things that may have been useful to us.

After this and some other issues are done, 0.2 should be released. 0.3 will
focus on stabilizing evaluation and adding more eval features.

@ayazhafiz ayazhafiz added help wanted Extra attention is needed e:2 Takes effort c:test a:lib a:bin labels Sep 29, 2020
@ayazhafiz ayazhafiz added this to the 0.0.2 milestone Sep 29, 2020
@ayazhafiz ayazhafiz modified the milestones: 0.0.2, Backlog Oct 20, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
a:bin a:lib c:test e:2 Takes effort help wanted Extra attention is needed
Projects
None yet
Development

No branches or pull requests

1 participant