genemish wrote:ok, strange things happening now..
Remember how it took 25+ hours (5 for import and 20 for housekeeping) to import 1.5MM hands (hence the thread).. during this process, i NEVER saw the postgres process even show up in the task manager...
Yesterday, i installed PT3 on my top of the line dell laptop (with SSD), and it took 5.5 hours for same process (2 for import and 3.5 for housekeeping) , during which the postgres process was going nuts in task manager.
soooo....
overnight, i received a 2nd batch (also 1.5mm) of hands to import and started on the SSD laptop first -- as expected, the postgres process was there all the time and importing took 4 hours and housekeeping is currently wrapping up (already on updating cache) and its taking a total of 8 hours. Yes, it's longer than 1st batch, but i am guessing that's because of presence of existing data which increases clustering size..
i started the same batch on the desktop (cause of this thread) and importing took 7.5 hours and clustering is at 3 hours at this point.. HOWEVER, i do not see the postgres process in the task manager..
---
my thoughts -- i must've botched up the PT3 and/or Postgres installation on my desktop. why is postgres process not showing up during housekeeping?????
my plan -- i did further research and figured that the WD VelociRaptor is very close in performance to SSD. especially dollar for dollar. So I will purchase this drive, remove PT3 and Postgres completely from my machine (uninstall, registry,etc)... and then reinstall everything on the new HD directly. (yes, i'll back up the "processed" folder and will reimport it after i am done)..
your thoughts?
some numbers after a recent re-import of all my hands:
reading from a samsung spinpoint F1 1TB hdd
writing to a western digital 300gb velociraptor
1st database:
importing 1.2M hands: 2h26m
housekeeping for that: 1h28m
2nd database:
importing 2.45M hands: 4h22m
housekeeping for that: 3h40m
3rd database:
importing 754k hands: 1h17m
housekeeping for that: 52m