Well, the .vmx file only has to be changed when using 4-core VMs, so if you were using 2-core VMs previously, you never would have had to worry about that.Well, I actually think I figured out most of my problem. I don't remember ever having to open the vmx file in wordpad and editing it but it was set to 2 processors so I changed that to 4 and now have 2 VM's going at about 4300ppd.
errr - meant to say two vm's going at 4300ppd eachNow if I can just get winafc to recognize my vmware session.....
Windows 7 = Yes, pro 64bit
VMware version = Player.
You want to change memory usage as well. I think it defaults to 512MB; for best results it's advised to use 1024MB or more.Well, the .vmx file only has to be changed when using 4-core VMs, so if you were using 2-core VMs previously, you never would have had to worry about that.
Default is 640MB. 1GB is enough for anything.You want to change memory usage as well. I think it defaults to 512MB; for best results it's advised to use 1024MB or more.
Default is 640MB. 1GB is enough for anything.
I was wondering about that, and after what you posted I decided to try it out. Now my VM is running with 8 cores as well (well, really 7 and a bit, with the other core going to the GPU).Wow, I had read that you could use up to 16 cores on ONE vm workstation with the new workstation 8.0 and they would be implementing it in vm player 3. Well, after realizing that I did infact have vmware player 3.0, I decided to give it a shot. And sure enough, works like a charm Sorry if this is old news but i think its pretty cool I have one vmware player session on my i7 and it is getting 8700ppd!
[18:09:55] Completed 57500 out of 250000 steps (23%)
[18:12:59] Completed 60000 out of 250000 steps (24%)
[18:16:00] Completed 62500 out of 250000 steps (25%)
[18:18:51] Completed 65000 out of 250000 steps (26%)
[18:22:09] Completed 67500 out of 250000 steps (27%)
[18:25:02] Completed 70000 out of 250000 steps (28%)
[18:27:50] Completed 72500 out of 250000 steps (29%)
[18:30:06] Completed 75000 out of 250000 steps (30%)
[18:32:18] Completed 77500 out of 250000 steps (31%)
[18:34:35] Completed 80000 out of 250000 steps (32%)
[18:36:46] Completed 82500 out of 250000 steps (33%)
Too good to be true. We tried this a while back with running 2-core VMs on one core each. Although the reported PPD numbers are large, that's because they're based on the log file frame times which are in turn based on the system clock of each VM. When you allocate a VM with a certain number of cores to a smaller amount of real cores, the system clock in that VM runs slower than real time which gives the illusion that it's more efficient than it really is.
Shouldn't make a difference.Is it currently better to be using the VMware Workstation RC (October build 197124) or switch to the released version of VMware player 3.0?
notfred's doesn't support bigadv workunits. You need to use a custom VM for that.Couple of questions:
1. How do I use the -SMP8 flag in notfred?
2. How do I set -bigadv flag in notfred?