As I suspected it was due to the almost empty results.txt file. As a result of this it was unable to figure out the 90% point properly on the next run, so anything new on that run were scored as negative numbers, so when all was restored to normal the change in score was significant enough for it to log a score changed date. I think that's a long way of saying it's a bugSpecifically, that there is a date under "Score changed" and this is the original appearance and score.
The attached graph shows the daily change in the various points. I've averaged over 5 days and removed the 100%, 98% 95% and 85% to make things at little smother and more readable.Could you post a diagram showing the derivation of these graphs? I'd love to see how much performance gain we have. Maybe we can even see some client changes in it?
Don't know why we had a big dip just over two months ago. Any ideas?
I'm now time stamping the data, so any graphs of this type in the future should be more acturate
Reply With Quote