How do you run your SMP clients?

How do you run you SMP Clients?

  • Windows (Native)

    Votes: 27 65.9%

  • Windows (Vmware)

    Votes: 2 4.9%

  • Linux (Native)

    Votes: 4 9.8%

  • Linux (Vmware)

    Votes: 8 19.5%
  • Total voters
    41
  • Poll closed .
I am currently running 2 clients under windows native on my quad, and 1 client native on the C2D.

 
Mostly I just try to run them on computers. Breaking down the code and using a calculator simply takes too long;)

 
I use notfred's diskless cd.......but, um....you already know that;)

Just thought I'd throw that out, it's been 100% stable for me lately.. no problems at all.

 
I haven't tried any VMs yet, but I already installed VMware on one of my machines and will attempt a quick Linux install with one SMP client and see how that goes. From what I've seen so far, I would much rather Stanford bring the Windows clients up to performance par than go all-out with the VM route. The additional configuration of all those VMs can be overwhelming, especially with a large farm and the lack of alternative OS familiarity, not to mention monitoring hassles and additional memory overhead. It can be really daunting if one has many machines. It's the main reason I avoided that route so far.

The only reason I'm even entertaining the idea is due to the fact my production is nowhere near where it should be with all the cores I have running. The brute force approach has its limitations.

 
Most in Windows natively with AC. One is a linux box and right now one is a notfreds diskless box.

 
digital_exhaust said:
I use notfred's diskless cd.......but, um....you already know that;)

Just thought I'd throw that out, it's been 100% stable for me lately.. no problems at all.

Click to expand...

Same here..... only problems I've ever had is if I try and push to much of an OC.

 
Pure SMP VM's here.

Once you have a disk image that works, then cloneing it is a five minute job.
Its making the disk image that does what you want it to, is the hard part.

Plus I'm running 99% p2605, which is probably the best protien to crunch.
If I dont get p2605, then I get p2563 which is the second best one to crunch.
Hence ~45k PpD from only 140 Ghz.

Luck ................. :D
 
Linux SMP on Ubuntu 7.10. However this is not a folding decision, I stop running Windows 7 years ago.
 
All 9 quads are windows native, with static IP addresses, dual SMPs.

Once the A2 core comes out I'll be dropping to Single SMPs as is suggested by F@H.

 
I sort of run a mixture.

Two of my quads are running Linux as host OS with two Linux VMs. These two boxen push 4500-5000PPD.

My other quad is my main system. It is currently running Linux with two Linux SMP clients natively for around 3500-4000PPD.

 
I have not yet spent the time to learn anything about linux other than the fact that it is free. I would like to eventually. Some of the people in my social life (read girlfriend) say I spend too much time with my computer as it is.

As a side note, for the first time the one in italics is winning.

 
SmokeRngs said:
I sort of run a mixture.

Two of my quads are running Linux as host OS with two Linux VMs. These two boxen push 4500-5000PPD.

My other quad is my main system. It is currently running Linux with two Linux SMP clients natively for around 3500-4000PPD.

Click to expand...

Same here. Most of my quads are running a Windows host and two VM's of Ubuntu 8.04 64 bit. I have one 3Ghz quad running PCLinuxOS as a host with two Ubuntu 8.04 64 bit VM's and its getting right about 12:05 a frame. I'll likely be converting most of my other quads to the same host/VM conbination in the future to get the same drop in frame times (hopefully).


 
I run my SMP via VMWare. All my VMs manage to pull nothing but 2605 and 2604 WUs. I love it.
 
I will expound on my previous reply now that this damn work computer isn't freezing up my system for 10-30 seconds at a time with only about 5 seconds to type something.

The reason my VMs are getting much better PPD is because they are pulling on 2605s almost exclusively. Because VMWare Server has a limit of 2 CPUs per VM, the F@H client identifies the quad as a dual core only machine. This way you don't get any or at least very few chewy work units since most of them are aimed at quad core machines. That's why my Linux install running two native Linux SMP clients don't get nearly the same PPD as my other two quads.

When I had my X2@3.0Ghz running the SMP client it was always pulling the 2605s as well. My main system actually pulled 2 2605s the other day and I was doing over 14k PPD between the three machines. If I was running F@H on my X2, I would have been doing almost 15.5k PPD between the 4 machines.

 
Windows native here, 2 x SMP and AC. It's good for 4200ppd on 2653's, but drops to about 3400-3600 if I'm crunching 3062's. Those are the 2 I usually get.



 
I have a big farm so there is a variety :

WinSMP exclusively at work with AC (dual-cores only)
laptop running native linux smp (dual-core)
1 Q6600 box running native linux smp for betatesting (ppd swing between 1900 and 5000 depending on what WU).
3 Q6600 box running windows as host and 2x linux SMP VM
1 Q9450 running windows and 2x linux SMP VM

The linux SMP VM is the best in terms of production but hopefully, this might change with the new A2 core.

 
I run the notfred diskless cd on both of my dual-core machines. I'm getting ~1760 PPD on a steady diet of 2605s.

 
You must log in or register to reply here.
Back
Top