PokerTracker

I don't know what you are using to parse the strings out of my tournament histories, but it must be junk.

My dual core CPU runs at 70%/50% for ~5 minutes, doesn't even finish the task. But all that heavy processing isn't a good thing for my CPU to do. It goes from about 42C up to 82C before everything starts crashing.

That's my problem, I know. But still: that's gotta be like more processing power than existed in the entire world in 1985. The equivalent of a few nuclear bomb simulations! Just to... parse some text? What in the heck is your code doing??

What version of PT3 are you using? (check the title bar of PT3)
Are you importing tournament hand histories or summaries?
Large summaries have a lot of database updates to make as you may have thousands of players to update.

I'm using the latest version. All I really want it to do is find my place and cash amount so it shows up in my graph. I guess maybe it's off creating DB entries for 20,000 newly seen players on the standings list; does anyone use PT3 in that capacity though? Even so, I'd expect it to get further through the list each time. I'm more suspicious that you have some thread stuck in some fast loop (e.g. time remaining never displays).

Please report your problem so that we can see what is going on.

If I run into the problem again, I'll submit a report and if it goes away I'll post back. I was hoping shame alone would be a motivating factor -- maybe per your latest release notes it was.

I must say: as someone who fixes programming bugs all day, I'm jealous of both your well thought out trace-debugging strategy and your ability to push back on customers for more info. My shop only has a dozen customers -- all household names -- and can't afford to lose one, and my OP is roughly as informative as the usual report I get in my inbox.

Next time I import I'll let you know.

The development team have found something to do with the email imports and in the next release they should be significantly (like an order of magnitude) faster.

Meh, still not working.

What's bizarre is if I copy the email into a text file, save it (in unicode format), and manually import that, everything is fine.

Aren't you just getting a text file from POP3? I can't imagine why your engineers would have different parser subsystems here if the text file import works.

But I can just work around this for now.

Conan776 wrote:I can't imagine why your engineers would have different parser subsystems here if the text file import works.

We don't. The emails get saved to a text file on disk and then read by the importer from disk.

http://www.aliexpress.com/store/product/New-CPU-AMD-Phenom-II-X4-955-Desktop-Quad-core-Socket-AM3-Socket-AM3/612048_571307064.htmlThis is the CPU,use good

That should work fine.