all the other projects work either faster or at the same speed as they did before i updated from 4.54 but cpdn has suffered a 50 percent increse in s/ts. it went from
10.37 as normal to 15.48. any ideas

---

boinc beta, predictor alpha/beta, lhc alpha/beta, cpdn alpha/beta

I don't have this version of boinc yet. And if I read what you experience i won't update actively to this versions. As far as i could read on the bouinc site the 4.5X is still in beta or? Then i wouldnt wonder if its slow because there is no single optimization in it for AMD nor Intel (or at leats i am not sure).

What i can tell is that the java environment is a veryvery serious problem in my opinion to the scientific programms (at all) and the way things are done within it. For instance: Setiathome Work Units took me about 2hours and 30 minutes to process on the old client (still c++/c) then the whole stuff was ported to BOINC which is either just java or a mix of java and c++ which I don't know exactly but there has to be a lot of Java in it as the Work Units needed 3 hours to process now. Then there was teh time when i had version 4.03 of BOINC and the processing of a setiathome Work unit even needed 5 hours!. Now i have 4.07 and the whole processing time seems to be back (nearly) on normal (known) values.

Just give it time and wait for a newer version of BOINC, i think you wont be able to do much about it atm.

---

> all the other projects work either faster or at the same speed as they did
> before i updated from 4.54 but cpdn has suffered a 50 percent increse in s/ts.
> it went from
> 10.37 as normal to 15.48. any ideas
>
I don't really know the answer to this, but the core client, which is CPDN version 4.04 I believe, has not been changed. So if there really is a slowdown due to the new install of BOINC, it has to be BOINC overhead, and soley due to its interaction with CPDN? Not impossible I suppose, but one would think the answer would lie elsewhere.

i actually forgot to check this. it was a computer issue not a software one. i defrag every week on sunday but i installed the sims and sim city plus boinc 4.56.
the two games are very large and around two thrids of the color was red and the other 1\3ish was green with a tid bit of blue thrown in there. the only time i had seen a worse one was the family computer. i started taking care of it in october when it got a virus. it hadent been defraged since we got it in dec 2003=@_@=

---

boinc beta, predictor alpha/beta, lhc alpha/beta, cpdn alpha/beta

> What i can tell is that the java environment is a veryvery serious problem in
> my opinion to the scientific programms (at all) and the way things are done
> within it. For instance: Setiathome Work Units took me about 2hours and 30
> minutes to process on the old client (still c++/c) then the whole stuff was
> ported to BOINC which is either just java or a mix of java and c++ which I
> don't know exactly but there has to be a lot of Java in it as the Work Units
> needed 3 hours to process now.

As far as I know boinc is ansi c (sience apps c/c++ and fortran)
where did you read that java was used (out of curiosity)

---

Florian
<a href="www.domplatz1.de">www.domplatz1.de</a>

&gt; What i can tell is that the java environment is a veryvery serious problem in
&gt; my opinion to the scientific programms (at all) and the way things are done
&gt; within it. For instance: Setiathome Work Units took me about 2hours and 30
&gt; minutes to process on the old client (still c++/c) then the whole stuff was
&gt; ported to BOINC which is either just java or a mix of java and c++ which I
&gt; don't know exactly but there has to be a lot of Java in it as the Work Units
&gt; needed 3 hours to process now.

&gt;&gt; As far as I know boinc is ansi c (sience apps c/c++ and fortran)
&gt;&gt; where did you read that java was used (out of curiosity)
&gt;&gt; Florian
&gt;&gt; www.domplatz1.de

I thought so too? I haven't seen any .java files in the BOINC source so far, only C source and header files, plus the program itself itself is an executable. Porting to Java doesn't make sense for a computationally intense application, CPDN especially.

I think the slowdown has something to do with how BOINC is structured or how the WU processing for SETI@home changed. I get a similiar slowdown, classic averaged 6 hours and now its 6.5 to 7 hours.

---

<p>
<img src="http://www.infinisoft.34sp.com/boinc/signature.php?project=sah&amp;id=7813418" border="0" />
</p>
</p>

&gt; I think the slowdown has something to do with how BOINC is structured or how
&gt; the WU processing for SETI@home changed. I get a similiar slowdown, classic
&gt; averaged 6 hours and now its 6.5 to 7 hours.
&gt;
Different slowdown than the one asked about by the first poster.

The one you mention is due to the Fortran compiler used in BOINC CPDN. While most Intel CPUs run a little, to significantly faster under BOINC CPDN, AMDs were either a little to significantly slowed down by the choice of compiler. AMD64s in particular have shown some significant slowdowns under BOINC. I'm seeing similar to you with my Athlon64 3400+. It was less than 5.5 hrs per trickle under classic and now is around 6 hrs. On the other hand, my P4 3.4 GHz improved from around 6.5 hrs under classic to 4.5 hrs under BOINC (running one model).

&gt; &gt; I think the slowdown has something to do with how BOINC is structured or
&gt; how
&gt; &gt; the WU processing for SETI@home changed. I get a similiar slowdown,
&gt; classic
&gt; &gt; averaged 6 hours and now its 6.5 to 7 hours.
&gt; &gt;
&gt; Different slowdown than the one asked about by the first poster.
&gt;
&gt; The one you mention is due to the Fortran compiler used in BOINC CPDN. While
&gt; most Intel CPUs run a little, to significantly faster under BOINC CPDN, AMDs
&gt; were either a little to significantly slowed down by the choice of compiler.
&gt; AMD64s in particular have shown some significant slowdowns under BOINC. I'm
&gt; seeing similar to you with my Athlon64 3400+. It was less than 5.5 hrs per
&gt; trickle under classic and now is around 6 hrs. On the other hand, my P4 3.4
&gt; GHz improved from around 6.5 hrs under classic to 4.5 hrs under BOINC (running
&gt; one model).
&gt;

I was referring to a SETI workunit, which I think is in C/C++. My CPDN trickle rate is a bit slow, my current model has about 50 hours CPU time but only 3 trickles (ouch). But your right this is a little off-topic from what the original poster was talking about.

Which reminds me I really need to think about defragging my old cruncher machine...

---

<p>
<img src="http://www.infinisoft.34sp.com/boinc/signature.php?project=sah&amp;id=7813418" border="0" />
</p>
</p>