Virtual Machines

[Dyyryath]

I've added two more machines to help our efforts by running the client under VMWare Workstation 4. I use VMWare's products pretty extensively both at work and at home. They allow me to do development work for several different operating systems at one time. It definately makes testing easier. :)

Anyway, it occured to me that I could set an upper limit on the amount of RAM that the client OS can access and keep things under control. It also keeps me from worrying too much about the client's stability. I'm not sure how much of a performance hit I'll take this way, but it'll definately give me better results than the alternative (not running the client on those boxes at all).

Has anyone else run the client in a VM before? I've used WINE in the past to run other DC clients under Linux, often with good results. We'll see how this works...

[IronBits]

Great thinking! Let us know how it works out :thumbs:

[Darkness Productions]

Any word on how well this works?

[Dyyryath]

I haven't been able to run a benchmark yet (it gives an error when I try to run the -bench switch under XP), but I can say that it's not exhibiting the same memory leak as the others. Strange. I'll have to leave it running for a couple more days before I'm sure, but so far, it looks pretty good:

http://www.zerothelement.com/offsite-images/dfp2-vm-ss.png

[Digital Parasite]

Originally posted by Dyyryath
I haven't been able to run a benchmark yet (it gives an error when I try to run the -bench switch under XP), but I can say that it's not exhibiting the same memory leak as the others. Strange.

Dyy, are you running:
.\foldtrajlite.exe -bench

You need the .\ for it to run under Windows. You can also try running it by clicking the "Run Client Bench" button from the Advanced tab of the new dfGUI v3.1 and it will launch the benchmark for you.

That is very strange about your VMWare copy not showin the "memory leak" as even the Linux version of the client does that...

Jeff.

[Dyyryath]

Yeah, the Linux copy is actually the one I'm using the most and it definately shows the leak. I'm not sure what the deal is just yet. I'm gonna dink with it some more tonight.

Thanks for the tip on the .\ for benchmarking. I'll try it and post the results when I get home. :thumbs:

It's kind of funny. I'm used to using ./ to launch an executable in the current directory with *nix, but it never occured to me to try it under Windows. :blush: