Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Tests should include some benchmarking #25

Open
ToxicFrog opened this issue Jan 29, 2015 · 1 comment
Open

Tests should include some benchmarking #25

ToxicFrog opened this issue Jan 29, 2015 · 1 comment

Comments

@ToxicFrog
Copy link
Owner

I've talked a lot about implementing things like an optional C backend to speed up vstruct, but how slow is it really? I need a way to consistently test performance so that I can tell what's actually making it slow, and whether the things I think are speeding it up really are.

At the moment the approach is to switch to ss1edit and time how long it takes to load ARCHIVE.RES, but that's not really a good solution.
@ToxicFrog
Copy link
Owner Author

fa84229 added some basic performance testing, but I want something more rigorous (and easier to use for regression testing) before I close this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@ToxicFrog