wow...I'll have to use that site more often! though, on my faster machine, the most recent WU is killing it. Then again, I think my clock speed may have gone back to stock somehow, I wish I knew of a utility that would report my cpu clock speed in linux.

Hey Neil, your bro's trend is going downhill. Oddly enough his spikes in completed WU's are spaced such that his 24 hr average is below mine, and yet he's leaving me standing still.

It's the luck of the draw, I think. He may be using his iMac Core Duo some of the time, too -- imagine that?! It seemed to do best with those 1760 point units (finishing every 44-46 hours), and the 1300 and 1500 point units are taking more like 50-52 hours...

You can run the SMP client on a P4 with HT and it will double your PPD.

Do a simple test:
Install the SMP client and run it. Install Fahmon and after a few steps (2 or 3) check if the WU will finish on time. if it does then you can run the SMP client successfully and it will boost you SMP.

I still haven't set up my X2 rigs,because it is proving to be a bitch to install lm_sensors in Ubuntu [6.10] (i thought ubuntu was supposed to be the most user-friendly distro? ). can someone walk me through it in tiny baby steps? I need to know temps are OK if I fold.

that, and I don't know about others, but I'm having serious issues with both the linux and windows SMP clients on two different machines...

I didn't want to hear that, I was planning on switching to SMP.

Well, after a week of SMP folding with linux, after a reboot, I started the client again. I woke up the next morning to a blank screen. Since then I was unable to get it to work until i downgraded my overclock. Not sure how, or why, but now I have instabilities, even though it was working flawlessly for over a week(not to mention I stress tested bot the cpu and ram for a day each).

As for the windows SMP client, I'm using it on a stock system running an AMD X2 4200. It will randomly pause and stop working, no errors, just no work is being done, and I don't realize it because I'm not monitoring it constantly.

We continually get 1 or 2 new folders every week BUT our total never changes because we keep losing folders as well.

Well, I got in trouble at school (long story), and my parents said I can't use my computer for a week. So I'd thought I'd put it to work.

I set up the console version (one instance) on my Pentium D 945 (3.4GHz), and it finishes a WU in 36-48 hrs. (Can't remember, will edit later) Since I've read that GPU folding is faster, I got the GPU client running on my X1950pro. Since the card is OC'ed via bios mod, it overheated in about 2hrs. So after a few flashes and DirectX installs, I got it stable again, and it completes a WU in about 13hrs! (8 min per percent) I wanted to say that I was really impressed at how fast my computer folded! Previously I was watching a 1.7GHz Pentium 4 fold, and it took 80 hrs to finish a WU! My graphics card folds six times faster than the P4! After seeing this success, I've decided to let the CPU [email protected] client run as a service (when I figure out how to do that ), and I'll run the GPU client at night and when I'm away at school.

Anyone have any predictions about how many ppd I'll be getting? And if I run the [email protected] CPU & GPU client when I play games, will it affect performance? I know it only uses idle CPU cycles, but how well does it dynamically reduce it's CPU usage?

Anyone have any predictions about how many ppd I'll be getting? And if I run the [email protected] CPU & GPU client when I play games, will it affect performance? I know it only uses idle CPU cycles, but how well does it dynamically reduce it's CPU usage?

I would guess it's around 550PPD, that's about what I was getting with my x1950pro. I stopped using it, because I get a lot more ppd using the SMP client. As for playing games, I wouldn't. I would also make sure you're only running a single threaded cpu client along with the gpu client. The gpu client needs to communicate with the cpu, so one of the cores needs to be free to do that. The gpu client doesn't take a low priority, it uses the gpu in full and that doesn't change, so you need to stop it before you launch a 3d intensive app.

I overclock my old Athlon XP machine, and [email protected] is an excellent long term stability test: it would be stable for a week or two and then I'd see a corrupted unit. I lowered the oc just a smidge -- and no more errors!

In my experience, the Linux SMP client is relatively stable -- there are installation issues around getting the 32bit libraries (for the client), but once it is going, the 64bit core is very fast, and stable.

The Windows SMP client and cores OTOH, are quite unstable. This is on the same (stock speed) Athlon 64 X2. From what I'm hearing, the Windows SMP client seems to work better on a C2D (larger caches?). I think the Athlon 64 X2 has an advantage in Linux - since the OS is 64bit, it can use all 16 main registers? And the client certainly works better in Linux, since it is used to form a "cluster" and is native to Linux. MS doesn't support clustering, and hence this drags the Windows version down, I think.

So after a few flashes and DirectX installs, I got it stable again, and it completes a WU in about 13hrs! (8 min per percent) I wanted to say that I was really impressed at how fast my computer folded!

Are you running XP?

_________________People who put money and political ideology ahead of truth and ethics are neither﻿ patriots nor human beings.

Who is online

Users browsing this forum: No registered users and 0 guests

You cannot post new topics in this forumYou cannot reply to topics in this forumYou cannot edit your posts in this forumYou cannot delete your posts in this forumYou cannot post attachments in this forum