Tests should include some benchmarking

Open ToxicFrog opened this issue 10 years ago • 1 comments

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.

Jan 29 '15 16:01 ToxicFrog

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

Oct 14 '16 13:10 ToxicFrog