If you shut down the system (always a good idea when swapping the CPU and/or memory) and insert the new CPU and memory, then power up and start BOINC, you WON't have to re-attach to the project, and you WON't get a new HOST-ID. When BOINC runs its benchmarks it also checks the CPU type, and will report the new values to the project.

Just as an FYI update, yup, that's exactly what happened...
I now have the 3700+ installed and it didn't assign a new host-id...

Brian

---

I'm currently running an Athlon64 3200+, Winchester core, with 1GB memory. I have ordered an Athlon64 3700+ San Diego core, which should be here first part of next week, and then I'm also getting (when it comes back in stock) a 2GB kit of memory. When I put in the new CPU, I believe I will show two hosts instead of one. Can I then merge the "hosts"?
What impact will the memory have as well? Will it cause the software to think it is yet another "new host"??

Thanks...

If you shut down the system (always a good idea when swapping the CPU and/or memory) and insert the new CPU and memory, then power up and start BOINC, you WON't have to re-attach to the project, and you WON't get a new HOST-ID. When BOINC runs its benchmarks it also checks the CPU type, and will report the new values to the project.

Did this a few times, no problems detected.

---

Join team BOINCstats

but be warned - this chip seems to have to "burn in" at stock speed for a while before it will stably overclock

Well, if you check out my times and compare them against other 3200+ cores,
you'll probably figure out I'm overclocked. I'm currently running it at
2520 @ 1.55-1.6v, which is beyond where you're at... :) Memory is running 1/1,
so it is DDR504, with 3-3-3-10 timing @ 2.8v (OCZ 3200 Platinum Rev 2).

There are three main reasons I'm getting the new processor:

* Lower voltage required, so I'm hoping to run at least the same speed with
1.45v, 1.5v max...which will reduce heat and power consumption.
* Improved memory controller so I can go to 2GB memory (OCZ 4000 Platinum EB)
* Both previous reasons so I can run VMWare comfortably

We have an influx of anti-Microsoft people where I work, so I'm needing to
learn some flavor of Linux and start coding some Java...and this route was
cheaper than getting a separate machine... I didn't go with the 4400 X2
because I will wait to go dual-core a year from now on Socket M2...

For both you and Hans, you really need to tweak the memory settings to
go as high as I have (or higher). You have to make sure to disable things
like Spread Spectrum (required for some parts of Europe though, I think)
and "Agressive timing". High quality RAM is also needed if you want to
let the ram run 1/1, otherwise you'll need to use the memory dividers to
scale back to DDR400 to DDR433... Personally, I don't trust the auto
overclocking built into the BIOS... I do it myself... :)

Edit#2 - Oh, and yes I've learned from reading tonight that I needed to
(and already have) install the optimized BOINC client due to low claimed
credit (in the teens usually). As for why I wanted to keep only 1 host,
I'm moving up fairly well in the 1-host rankings... Yes, I know...
"It's about the science..." :P

Brian

---

Did you raise CPU vcore?

No, no need to yet...

Fine :o)

I wouldn't like to raise Vcore because the power consumption goes up pretty steep
with higher voltages.

I couldn't get at 10% OC at the first try, will be trying 5% for a while now.

Thanks.

Regards Hans

---

Did you raise CPU vcore?

No, no need to yet... the only thing I've changed is the basic clock speed. Haven't adjusted ANYTHING else. When I first started, I went to 5% (all was ok) then 8% using the MB-supplied overclock utility (Windows app) and everything got flaky; lockups, crashes, etc.; went back to normal, everything ran fine, I figured I was out of luck, wouldn't be able to overclock this chip. Read a lot, found a site that talked about needing to burn-in, so I let it run for a week, tried again, and it was fine at 8%. Decided I didn't like the "automatic everything" approach the Windows app takes (it adjusts memory speed, voltages, etc., all you pick is a "percent overclock") and went to using the raw BIOS settings. No problems with 10% bump and no other changes; letting it run like that for a while, then I'll step up speed until I see a problem, then decide if it's likely the problem is from low Vcore or from RAM speed...

If I can avoid raising the Vcore, I'd prefer not to. I'm trying to keep the temperature down with just the stock cooling. The reviews of the 3700+ I read (from people who know a WHOLE lot more about overclocking than I do...) were impressed with how far they could push it on stock voltages. I want to stay well under the point where any problems at all are likely to appear that might damage anything!

But be warned - this chip seems to have to "burn in" at stock speed for a while before it will stably overclock, so now I'm taking it up in small steps.

Hi Bill,

Thanks for the hint!

I didn't have much luck when trying to overclock my 4400+, but I'll give
it another try.

Did you raise CPU vcore?

Regards Hans

---

I have ordered an Athlon64 3700+ San Diego core

For your question - what Hans said. But I can _almost_ guarantee you won't be able to merge, with different CPUs. Memory shouldn't matter. However, all the projects sometimes randomly decide you have a new computer, so...

From me - you will LOVE the 3700+. I just recently built a "cruncher" using that CPU. I've overclocked it 10% (2420MHz) and it's running at 44 degrees C - LOTS of room to overclock it further, which I plan on, but be warned - this chip seems to have to "burn in" at stock speed for a while before it will stably overclock, so now I'm taking it up in small steps. With optimized BOINC client and optimized SETI app, it does a SETI WU every hour (57 min avg), and averages 19.21 credits per WU. That's almost 480 credits/day if I was running only SETI.

I'm currently running an Athlon64 3200+, Winchester core, with 1GB memory. I have ordered an Athlon64 3700+ San Diego core, which should be here first part of next week, and then I'm also getting (when it comes back in stock) a 2GB kit of memory. When I put in the new CPU, I believe I will show two hosts instead of one. Can I then merge the "hosts"?
What impact will the memory have as well? Will it cause the software to think it is yet another "new host"??

Thanks...

You can have as many hosts as you like, no problem there.
If you can't merge, just wait until all results of the old host have disappeared. (*)
Then you'll be able to remove it.

Regards Hans

(*) This might take quite some time, but will work eventually.

---

I'm currently running an Athlon64 3200+, Winchester core, with 1GB memory. I have ordered an Athlon64 3700+ San Diego core, which should be here first part of next week, and then I'm also getting (when it comes back in stock) a 2GB kit of memory. When I put in the new CPU, I believe I will show two hosts instead of one. Can I then merge the "hosts"?
What impact will the memory have as well? Will it cause the software to think it is yet another "new host"??

Thanks...

---