New Software Announcement - SIXTH SENSE

[SixthSense]

[ QUOTE ]
yes any experienced PT user knows that but the ptagg database importing has crawled to 15K per hour after about 4M hands total aggregated.

When I first started aggregating hands i recall the rate was at ~30K-40K hands per hour.

[/ QUOTE ]

Yeah, that's about what I'd expect, its slowing down to about 1/3 of its original speed because there are lot more records in the database. I'm not saying that's a good thing, but it is expected.

Sorry, I didn't mean to sound like I'm avoiding the issue. But its unlikely that there's anything I can do to PTAgg to speed it up any more.

I think you really answered the question - the best solution is to just import the most recent data into PTAGG. I wouldn't even bother importing any db's that are more than 6 months old.

Lastly, it sounds like a new computer could help speed it up for you. Since you are only getting 40k hands/hour to start with, that's about 1/2 as fast as my machine, and mine is a few years old. Just an option to consider.

-Ben

[Back In Black]

[ QUOTE ]
I think you really answered the question - the best solution is to just import the most recent data into PTAGG. I wouldn't even bother importing any db's that are more than 6 months old.

[/ QUOTE ]

??

[ddubois]

I can't find anything on the website about the function, maintenence, or performance of PT Aggregator. I presume it's a tool for people who have multiple large databases to create some sort of summary cache, but there should be a description somewhere, IMO. I have my databases separated by year, then by limit vs NL, so I think I don't need PT Aggregator at all, because I'm only looking at one databases at a time, but I would like to see all aspects of PT Aggregator clarified in one place.

[SixthSense]

[ QUOTE ]
I can't find anything on the website about the function, maintenence, or performance of PT Aggregator. I presume it's a tool for people who have multiple large databases to create some sort of summary cache, but there should be a description somewhere, IMO. I have my databases separated by year, then by limit vs NL, so I think I don't need PT Aggregator at all, because I'm only looking at one databases at a time, but I would like to see all aspects of PT Aggregator clarified in one place.

[/ QUOTE ]

Sorry, we do need to add more docs to the website. You can start PTAgg from within "Config DBs", then click PTAgg's help button to get a brief description. We will add more to our website soon.

-Ben

[2easy]

[ QUOTE ]
[ QUOTE ]
please, let's try to figure this out. as i said, i have already signed up for the full meal deal. now id just like to get things working right.

[/ QUOTE ]

Oops, sorry if I missed that.

Other things to try are to shut down PT Aggregator's import while you are playing, and just start it up again when you are done.

And if you aren't running the de-monster script I still think that's worth at least trying.

-Ben

[/ QUOTE ]


sigh. ok, let me try for the third time.

[ QUOTE ]
i have demonster.ahk (script) running at all times, regularly defrag, full vacuum daily, etc..

[/ QUOTE ]

and:

[ QUOTE ]
anyway, going from a 60 second "pull" to a 45 minute "pull," is attributing quite a lot to "monster", even if that were the case. everything was the same, i was pulling from the same tables, etc., same configurations, etc., the only difference being using the aggregater or just using my main db.

[/ QUOTE ]

1)it's not a monster problem.

2)i AM running the "monster script"

3)if it were a monster problem, then why a 60 SECOND update/refresh with my main db and a 45 MINUTE refresh/update when using the aggregater?

4)i DO use the aggregater as you suggested; i.e., off when playing, then on afterwards.

5)please address the questions that im trying to get answered, taking into the account the information that i give/have given you.

6)i'm still hanging in there. let's try to get this working right for me, please. [img]/images/graemlins/crazy.gif[/img]

[SixthSense]

[ QUOTE ]
1)it's not a monster problem.

2)i AM running the "monster script"

3)if it were a monster problem, then why a 60 SECOND update/refresh with my main db and a 45 MINUTE refresh/update when using the aggregater?

4)i DO use the aggregater as you suggested; i.e., off when playing, then on afterwards.

5)please address the questions that im trying to get answered, taking into the account the information that i give/have given you.

6)i'm still hanging in there. let's try to get this working right for me, please. [img]/images/graemlins/crazy.gif[/img]

[/ QUOTE ]

OK, I see you are running demonster already.

Let me see if I understand the situation correctly.

You startup Sixth Sense with *nothing else running*. You set it to NOT use PTAggregator. You clear the stat cache, do a Refresh, and it downloads X tables (how many?) and scores them in 60-90 seconds.

Next, you set Sixth Sense to use PT Aggregator. *Nothing else is running still*. You clear the stat cache, do a Refresh, and now it takes 45 minutes to score the tables.

Is this correct?

UPDATED - I think I might know what the problem is. I'm posting a new build in about 15 minutes that will have an Advnaced Option (CTRL-O) to change SS's process priority. When that comes out try it again with that set to "High".

-Ben

[SixthSense]

v1.0.0.48 - 8/24/06

- Added: While the trial is active, a warning dialog is shown, for how much
time is remaning for the trial. This is only displayed ONCE per session.
- Added: New Advanced Option "CPU Priority".
- Options are Normal, Higher, Highest
- It now defaults to "Higher"
- Using anything but "Normal" might cause your other apps to slow down,
especially when SS is scoring tables
- Changed: Manage Subscription Dialog now uses server to calculate trial
time remaining and subscription time remaining. This fixes a timezone
bug related to the trial time.

-Ben

[r0eKY]

[ QUOTE ]
v1.0.0.48 - 8/24/06

subscription time remaining.
-Ben

[/ QUOTE ]

this is going to be subscription only??

im not paying more than $20 one time, this whole SS thing has cost me alot of time and money and it's still slow and i never see it working fast and easy

[2easy]

[ QUOTE ]
OK, I see you are running demonster already.

Let me see if I understand the situation correctly.

You startup Sixth Sense with *nothing else running*. You set it to NOT use PTAggregator. You clear the stat cache, do a Refresh, and it downloads X tables (how many?) and scores them in 60-90 seconds.

Next, you set Sixth Sense to use PT Aggregator. *Nothing else is running still*. You clear the stat cache, do a Refresh, and now it takes 45 minutes to score the tables.

Is this correct?

UPDATED - I think I might know what the problem is. I'm posting a new build in about 15 minutes that will have an Advnaced Option (CTRL-O) to change SS's process priority. When that comes out try it again with that set to "High".

-Ben

[/ 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. it took about the same times for each type, (main db/ptagg.) about 15 seconds for main db scoring and a little less than 5 minutes for ptagg scoring.

edit to add p.s.

when it was taking 45 minutes using the ptagg to score (approx. 110 tables,) i was running other programs, i.e., pt, pahud, and 4 other poker sites besides party.
however, it was only taking about 60 seconds to do a scoring when using only the main db, even with all of these other apps running.

i haven't yet experimented with ss with these other apps running since the update.

[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