Athon 64 x 2 @3GHz or Phenom 9550 @ 2.4GHz |
![]() |
| log in |
Message boards : Number crunching : Athon 64 x 2 @3GHz or Phenom 9550 @ 2.4GHz
| Author | Message |
|---|---|
|
My computer ID: 5940401 has been running for a long time with an Athlon 64 x 2 5800+ slightly overclocked via FSB only, to just about 3GHz. | |
| ID: 1192166 · | |
|
Should go up. As long as the GPU's RAC stays somewhat steady, the CPU crunching has gone from 1x3GHz to 3x2.4GHz (effectively 7.2GHz). The task durations will increase, but you are doing ~233% the amount work in the same period of time on CPU. | |
| ID: 1192168 · | |
Should go up. As long as the GPU's RAC stays somewhat steady, the CPU crunching has gone from 1x3GHz to 3x2.4GHz (effectively 7.2GHz). The task durations will increase, but you are doing ~233% the amount work in the same period of time on CPU. But I've slowed the CPU-portion of the processing for the GTX460. I noticed that the "free core" was staying about 50% busy, which is a little high. If I slow the GPU, even a little, there's no way that the extra 2 cores at 2.4GHz can possibly overcome the loss. | |
| ID: 1192197 · | |
|
I'm not even sure why you stopped using the 1 core in the first place. The amount of CPU use is minimal on Multibeam tasks. You may notice a few minutes added to your crunching. | |
| ID: 1192224 · | |
|
A GTX460 doesn't stress a dual core 3200+, never mind a quad core phenom, so don't bother reserving one core to service the GPU, just let everything crunch and gain a few hundred more a day. | |
| ID: 1192249 · | |
A GTX460 doesn't stress a dual core 3200+, never mind a quad core phenom, so don't bother reserving one core to service the GPU, just let everything crunch and gain a few hundred more a day. Good advice. I can personally vouch for that. No need to reserve a core. Regards, A ____________ | |
| ID: 1192258 · | |
A GTX460 doesn't stress a dual core 3200+, never mind a quad core phenom, so don't bother reserving one core to service the GPU, just let everything crunch and gain a few hundred more a day. Unless you're running the Nvidia OpenCL Astropulse app, and have 270.xx or later drivers, then a full core is required to feed the app, otherwise it just stutters along, Claggy | |
| ID: 1192262 · | |
I'm not even sure why you stopped using the 1 core in the first place. The amount of CPU use is minimal on Multibeam tasks. You may notice a few minutes added to your crunching. Seems reasonable to me, so next time I'm at the computer I'll add the other core to crunch and we'll see how that goes. | |
| ID: 1192266 · | |
|
Hey! | |
| ID: 1195826 · | |
|
confused... So the RAC dropped after adding the Core or before? | |
| ID: 1195853 · | |
confused... So the RAC dropped after adding the Core or before? skildude - I'm being "funny." I didn't get a chance to add the last core before I ran out of CUDA work, which is funny because I was worried about the CPU not being able to feed the GPU fast enough. The RAC is falling because we're out of work. It was "gallows humor." | |
| ID: 1195881 · | |
Should go up. As long as the GPU's RAC stays somewhat steady, the CPU crunching has gone from 1x3GHz to 3x2.4GHz (effectively 7.2GHz). The task durations will increase, but you are doing ~233% the amount work in the same period of time on CPU. Not only the clock is important. The Phenoms always do more MIPS than Athlons at the same clocks on my systems. EDIT: Example: This Athlon x2 runs @2200 and this Phenom x3 runs @2100. Compare the benchmark results for yourself. ____________ | |
| ID: 1195944 · | |
confused... So the RAC dropped after adding the Core or before? I thought that was reserved for the RIP skildude thread ____________ Proud member of TSWB. End terrorism by building a school | |
| ID: 1195980 · | |
Message boards : Number crunching : Athon 64 x 2 @3GHz or Phenom 9550 @ 2.4GHz
| Copyright © 2013 University of California |