[SixthSense]

[ QUOTE ]
pretty much correct.

i have had other things running using ss both ways, (i.e., from main db only and using ptagg.)

and yes, about 60 seconds using main db, and 45 minutes using ptagg.

i downloaded the new update, (vers. 1.48,) and ran some tests, as you suggested.
scored tables *with nothing else running* using main db only, (after clearing cache.)
it scored 110 tables in about 15 seconds.
did the same using ptagg, it scored the same 110 tables in 5 minutes. (with nothing else running.)

experimented with changing priority from normal, to higher, to highest. found little to no difference in any of the runs. about the same times for each type, (main db/ptagg.)
about 15 seconds for main db scoring and a ltille less than 5 minutes for ptagg scoring.

[/ QUOTE ]

OK, so we at least are making progress. We've gone from 45 minutes scoring with ptagg downto 5 minutes. How many tables is this for? If its 100+ tables, I'd say we are in the acceptable ballpark. And with the stat cache kicking in on subsequent scoring, it will be faster.

It is strange that the NON-PTAgg method is so much faster than PTAgg. I think you should still use PTAgg, as it has the complete data. You do have your LARGEST db at the TOP of the list in "Config DBs", correct?

Do you agree that 5 minutes to score the tables the first time, with subsequent scoring being faster is acceptable? I hope so, because there's probably nothing I/we can do to speed that up anymore (short of buying a new PC). [img]/images/graemlins/smile.gif[/img]

-Ben