The Tournament Director Forums
Main => Suggestions => Topic started by: UPT on February 26, 2008, 07:28:28 PM
-
Any chance of releasing a Standalone Statistic Compiler?
It can take a long time to run some stats and you can do nothing in the TD while it is going on.
I think it would be a great addition.
(I am currently wanting to crunch 1442 tournaments.)
-
I can certainly appreciate why you would want this, but frankly I think yours is a unique situation. Unless someone else out there is running stats with over a thousand tournaments? Anyone? Anyone? Bueller?
So, uh, yeah, how long does it take to process 1442 tournaments?
-
;D
Well as it goes along it gets slower and slower.
Last night I did 382, the longest wait is once it is done.
The wait for the final numbers is about 10 minutes for 110 tournaments.
In December I crunched about 700 of them and it took over a day to run them and have it spit them out ;) I think the version of TD I was using then was a little slower than the current version. I recall at some point last year the stats slowing down considerably.
The stats that the TD tracks is IMO one of the strongest features... I am a baseball nerd from wayback... I love the stats.
But I will track the times as I run them this weekend and let you know.
The specs on this "cheap" laptop are as follows...
AMD Mobile Sempron 3000+ / 1.8 GHz with 256 MB
I need to get the TD running on a desktop again.
-
Interesting. What I think I noticed in the past few months is a speedup not only in the TD but in another [personal] application I use that shares some of the codebase with the TD. I feel like Microsoft did something that sped up IE/Jscript, because the speed increase was significant for me to simply notice that things were running faster. This happened on every PC I use the apps on, and I don't know what I could have done to the code to account for the speed increase (well, the core of the app has undergone quite a bit of change for 2.5, but still, nothing really *specifically* to try to speed it up). I also don't remember a corresponding Windows Update that would explain it, either... ???
Oh well, don't look a gift horse in the mouth, and all that.