PT4 beta *Virtual Machine* posts

[G3K0]

Thread for VM specific remarks.

Thought we could gather our observations under one thread.
On configuration specific posts, please ensure to list your PC Spec, Host OS, Guest OS and PT4 version.

[G3K0]

Macbook Pro 13" Mid-2010 edition
2.4 GHz Intel Core 2 Duo
8Gb 1067 DDR3 RAM

OS Lion 10.7.3 Host OS
Win 7 Ultimate 32-bit Guest OS @ 4Gb RAM

PokerTracker 4 Beta v.4.01.8

Many VM setups will be very slim, just enough room for Guest OS + a few apps in the Virtual Drive so beware where your PT4 installation is moving processed hands to. Prior to 1st import via Set-up wizard, quit the set-up wizard and change the folder where PT4 moves processed hands which defaults to:

Code: Select all

c:\user\app data\local\PT4\Processed

You configure the processed output folder under the Configure / Site & Import Options menu option.
You may then re-run the 1st use Wizard from the Tool menu

It's a good idea so segregate new processed imports to PT4 in their own separate directory so that you can keep your existing PT3 db current by doing a directory import in PT3.

Ensure to install your PostgreSQL DB to the Host OS otherwise, like my first installation, you will be likely to see significant performance degradation.

For guides on Mac Os X Lion PostgreSQL installations see this thread, this thread and this thread.
For a guide to configuring your PostgreSQL DB to broadcast across your Host to the VM OS, and your PT4 connection see this thread.

This may have been particular to my installation(s) but I have found that if your PokerStars saved hand histories are saved to your Host OS then there are issues with the detection of files to monitor during the session import in PT4. New tables may not be recognised and thus the HUD will not be displayed as PT4 is not noticing when new HH files are being added to the watch directory(ies).

To resolve this phenomenon, configure your Win PokerStars client to save the HH to your Guest OS and set PT4 to watch that directory. PT4 will then pick up all new tables and display the HUD correctly.

All in all PT4 has proven to be a slick piece of kit after ~1 week of testing, more posts / observations to follow.

[kraada]

Great post G3K0 - thanks!

[PJs Ronin]

Custom Desktop based on GigaByte MOBO and Core 2 Duo 2.8GHz (time for a new system I know)
4GB DDR2 Ram
nVidia GeForce 8400 GS (saddly, 512MB only)

Ubuntu 10.04LTS (Lucid Lynx) Host OS
Windows XP 32 bit SP3 (modified) Guest OS with dot Net 4.0. 10Gb image.
Postgres v9.0.5
VirtualBox v4.1.08 with Guest Additions

PokerTracker v3.11.9 beta
PokerTracker v4.01.8 beta
Competitor (Brand Y) v1.12.09
Competitor (Brand Z) v2.0.0.6309 (test)

Storage. 1Tb 7200rpm HD, no SSD

Putting postgres on the Linux side is the only way to go, however this will introduce a backup limitation that resides in postgress, not the tracking software.

Hand Histories / Archive
I have it set so that only PT4 provides the HUD and therefore the auto HH import. I allow PT4 to moved the HHs to the default 'processed' sub-directory. Daily, I use Brand Y to auto-import from the PT4 processed subdirectory and archive the HHs to a shared network drive under Z:\PokerArchive\yyyy\mm\dd. I then update the other trackers by doing a manual import from the appropriate sub-directory. The reason I do this is twofold. First, I like to ensure the data provided by one tracker is verified by a completely different tracker. Once I'm really comfortable with PT4 I'll wind back on the others. Second, I don't like the PT4 archiving schema. I'd recommend PT4 developers look at the archiving system as the date format introduced about a year ago was, imo, done in haste and was not the optimal solution.

Data Backup
You can't do a full backup (sic) of your 'poker stuff' if postgress or the db is on a network drive (postgres limitation). I use pgAdmin to go through my 4 dbs and make a backup of each to the shared directory z:\PokerBackup\. I then use each of the trackers to make backups of all their parameters/configurations/filters/etc (except the db) also to z:\PokerBackup\. Weekly linux cron jobs then compresses everything in z:\PokerBackup and z:\PokerArchive and outputs everything to a removable 1Tb HD. May be convoluted, but it works.

The VM
Keep this as light as you can. I use Win XP for two reasons. First, it's been around long enough so that most of the major headaches have been overcome. Second, it is the only version where you can get past Bill's registration process that limits you to using your licence only once. The only thing you should have running in the VM is poker clients, trackers (and in my case, .Net) and a browser. Dump IE and FF and use Chrome, it's more secure and faster.

I do NO browsing in the VM, nor do I install programs that are 'fun, exciting and free' and thus I have no anti-virus anti-anything installed. If by some miracle I do get an infected VM, I blow the whole thing away and reload from a backup... easy peasy. My VM image is 10Gb and I cron a monthly backup of the entire image to (you guessed it) a removable 1Tb HD.

Performance
My idea of multi-tabling is 2 x SnGs, 1 x FR PLO cash table and a Nina Simone MP3 (on the linux side) with poker data no more than 12 months old. Linux is rock solid, the VM is exceptionally stable and Win XP is the best of a bad bunch. Tuning postgres is a necessity and Derek gave some great advice on how to do this here.

It takes some additional work to manage VMs, but if you're reading this thread about VMs and host o/s, then maybe it's what you're looking for. Kudos to G3K0 for trying to get this all in one place. Oh, and the PT support folks know a thing or two about this.

Note. No, I will not provide any comparisons between the trackers.

[WhiteRider]

Second, I don't like the PT4 archiving schema. I'd recommend PT4 developers look at the archiving system as the date format introduced about a year ago was, imo, done in haste and was not the optimal solution.

How would you like the Processed folder to be structured?
Personally I disable the date option and just use the by-site option as I find it easier to find files that way. (Configure > Sites & Import Options > Preferences)

[PJs Ronin]

@ WR

yyyy/mm/dd rather than yyyy/mm-dd

[PJs Ronin]

I know a few folks who are running Windows XP as a VM guest as XP is still a viable option for running programs that will not run under anything under than Windows. The problem with this (and pretty well any Windows o/s) is that over time the o/s becomes bloated and that impacts performance. If you're running Windows in a VM, typically your focus is on performance rather than bells and whistles. Time for a clean up.

I had a look at a Black Viper article on reducing the standard XP services down to more trim level. I selected the 'Tweaked' settings and my VM went from about 35 processes, 300-320Mb Page File memory usage and a resting CPU usage of about 5-8%, to 18 processes, 180Mb PF mem and resting CPU of 1% and that's now WITH PokerTracker4.exe and PokerTracker4Hud.exe running, but with no poker clients. On my system, this has been a substantial performance improvement.

The article is here and I'm guessing that with a look around on his site you'll likely find performance tips for other Win o/s versions.

[kraada]

Thanks! As someone who also uses an XP VM I'll definitely take a look at this.

[G3K0]

kudos Ronin, very helpful post.

[G3K0]

4.01.17 seems to have degraded VM hosted Postgres db performance.

I'll try and get a firmer / more detailed analysis as opposed to that pfft a>b statement ^.
Any other VM users experiencing performance differences after this release for running reports and returning DB queries?

cheers.
G3K0-

Macbook Pro 13" Mid-2010 edition
2.4 GHz Intel Core 2 Duo
8Gb 1067 DDR3 RAM
Postgres 9.05

OS Lion 10.7.3 Host OS
Win 7 Ultimate 32-bit Guest OS @ 4Gb RAM

PokerTracker 4 Beta v.4.01.17