Slow Import Speed

[pat3392]

Would purchasing a SSD be the best way to go about this? Have I got any other options to increase the reading/writing speed, other than the tuning information provided in the guides? If I purchase a 256gb SSD, and I run out of hard-drive space, will there be a way of adding hard-drive space that doesn't involve me having to reimport my entire database to somewhere else? In other words, can I make the hard-drive space scalable?

[kraada]

Scaling can be done though admittedly it's not an easy process.

However if you're dedicating a 256G drive to PostgreSQL it's very unlikely that you run out of space. Since 1M hands is roughly 10G of space, a 256G drive will give you roughly 25M hands worth of room - that's a lot of data!

[pat3392]

I don't view 25 million hands as much, if I wasn't having these technical issues I'd probably be on my way to filling that up.

I'm trying to gauge what kind of life expectancy I'd get out of one of these. I can't calculate it, because I don't kno how much writing PT4 will actually do. Have any approximation?

What can I do to backup the SSD?

How much RAM would I need to take full advantage of the SSD?

Would using postgreSQL version 9.0, 64 bit version be fastest? Could there be any potential problems with this?

[kraada]

The last I checked into SSDs the number of reads and writes before failure had gotten very large - into years of continuous reads and writes - and since PostgreSQL only reads and writes while you're playing poker and you aren't going to play 24/7 for years (I imagine), I wouldn't really worry about that too much.

The PT3 backup system works just fine on SSDs or any other type of system.

If you have a 64 bit machine 9.0 x64 would almost certainly be the best fit for you; once you have a 64 bit machine the more RAM you have the better (if your entire database can fit in RAM you get a massive performance boost). I wouldn't build a new machine for myself with less than 8G for certain at this point. Everything will run on less of course, but since RAM is cheap . . . why skimp on it?

[horse2102]

hallo,

i am in a similar situation. just moved from hm1 to pt4. have a brand new pc setup and all, but import speed is very slow. for example, i started importing hands last night and this morning, just a fraction was imported.
my old hm1 db was approximately 180gb big which i guess is around 18m hands. now importing 600k hands takes a whole night!!

im using a 250gb ssd and 64bit sql 9.0xx. 16gb ram, intel xeon cpu


any tipps on how to migrate my old DB? i still have it in its original sql8.4 folders on a seperate HDD....


greets

[horse2102]

found this via search function... just noticed this is pt3 forum..
so pls move it if necessary. i just need to know how to get my old DB back while not having to wait like 20 days for pt4 to import

[WhiteRider]

Importing that many hands will take a considerable amount of time. If you split the import up into smaller batches of files you'll probably find it a little faster overall, and you'll be able to use PT4 in between imports.

[horse2102]

is it normal, that importspeed drops significantly after about an hour?

i cant import 4000 files 10 at a time just because you get down to like 20 hands/s after a couple of hours, can i?

[WhiteRider]

Import speed does drop over longer imports but if you have a lot of files to import it will be easier to do batches of more than 10. With some experimenting you'll probably find a good batch size to import overnight or whenever, so that you can use PT4 and import your old hands during your downtime.