[SixthSense]

[ QUOTE ]
[ QUOTE ]
not even

[/ QUOTE ]
I want to retract that ...last couple nites I only was able to import two-three thousand hands each nite but today PT Aggregator just downloaded 400,000 hands in only 3 1/2 hours so perhaps I was hasty in my assesment-thats a huge improvement. [img]/images/graemlins/blush.gif[/img]

the program seems to run much better a fresh reboot and having absolutley nothing else runing-I havent even restarted PT Aggregator-just left it up for 3-4 hours.

Last couple nights I just launched PT Aggregator after long playing sessions and did not reboot.

not sure what the cause but yea at 100k hands imported per hour 2.3M db would take ~23 hours if this pace stays steady. Reason I mention it is I have 4 or so more big db's I'd also like to aggregate.

Is there a limit to how many databases I can aggregate separately or in total?

Excuse my ignorance but what happens to this aggregated data and where does it go?

[/ QUOTE ]

OK, good, that sounds more like how it should run.

No, there's no limit to how many db's you can aggregate. Just your disk space I suppose, but that really should not be a problem. The aggregated database holds 1/10th to 1/100th of what the normal db's hold.

It gets placed in a PostgreSQL database called "ptagg", you can look at it using the PGAdmin III tool that came with Postgres.

-Ben