Can I disable temporary vmem files?

[quiettime]

I'm using VMWare Workstation 10 on a Windows 7x64 host and running a Windows 7 x64 guest. I would like to stop arbitrary vmem writing because it causes freezing. I am aware vmem files are used for snapshots and that's fine since I initiate them but I mean the sporadic files that are created that look like "VM Name-Random Chars.vmem", for example "Windows 7-1afeb2cf.vmem". The disk IO is just too intensive.

Several years ago I asked about stopping vmem writing and the setting mainMem.useNamedFile = "FALSE" was mentioned so I added that in C:\ProgramData\VMware\VMware Workstation\config.ini

Since that time I have changed computers and am now using VMWare Workstation 10 with that setting, but I have swapping partially enabled, it seems:

Edit > Preferences > Memory > 'Allow some virtual machine memory to be swapped'

Does anyone know what those temporary vmem files are? Are they a swap file and can I disable them by setting 'Fit all virtual machine memory into reserved host RAM' or if not what should I do?

Thanks

[continuum]

mainMem.useNamedFile = "FALSE"
only makes sense if you also set

prefvmx.minVmMemPct = "100"

MemTrimRate = "0"

mainMem.useNamedFile = "FALSE"
is something you have to pay for:
for suspend and resume you need a file with the size of the configured vRAM
If you dont have a named vmem-file in VM-dir every suspend action creates a new one that needs a random-name.

[shellycat]

I had a similar problem.  See the thread, where I posted about a support suggestion.to solve what sounds

like a very similar problem

Re: Workstation 11 .0.0 Build-2305329 hangs - Win 8.1 host

See page 3 for the fix settings. It does not affect the ability to suspend/resume.

I think vmware 11 has a problem with the way they store memory by default on Windows. 

[quiettime]

Thanks so much guys. I'm trying out these settings now, I'll see how they go for a while:

prefvmx.minVmMemPct = "100"
MemTrimRate = "0"
mainMem.useNamedFile = "FALSE"
sched.mem.pshare.enable = "FALSE"
prefvmx.useRecommendedLockedMemSize = "TRUE"

Also, related to this, I have gone through my history and I now realize that I probably unwittingly wiped out my configuration a few times since VMWare Workstation chokes on INI comments and can destroy configuration prefs in those cases. I just filed a bug about it here, watch out:

Workstation 10 wipes out parts of config.ini if comments are used