After a few hours SETI, einstein, and predictor are working well with BOINC 4.19. With BOINC 4.18 instead of 9 to 9.5 hours, it only took 4.5 hours to complete a seti work unit. (12 seti hours with BOINC 4.16)I have noticed no other change in either BOINC 4.18 or 4.19. I like einstein and don't mind frequent upgrades as a part of really being a part of the ever changing frontiers of science.

---

HI

Four posts, one should be enough.

greetz Mike

---

With each crime and every kindness we birth our future.

Using 4.19 for several hours now and no problems in any of the projects: CPDN, SETI, Einstein, ProteinPredictor (all 4 running ok).

Have Pirates and LHC but no work from them.

---

Patience is a virtue.

Is someone using a Proxy?

I have installed 4.19 but everytime it tries to connect I get an error.
When installing again 4.13 I don't get this error and Boinc can connect.

In both the proxy is set correctly.

---

<a href="http://boinc.blogspot.com">Boinc y Astronomia</a>
<br>
<img src="http://150.214.190.154/BOINCStatistics/Signature/XnXnX/jgh/x.png" />

> Is someone using a Proxy?
>
> I have installed 4.19 but everytime it tries to connect I get an error.
> When installing again 4.13 I don't get this error and Boinc can connect.
>
> In both the proxy is set correctly.
>

Maybe this is of help?

---

Aloha, Uli

Thought it was ok, until it rebooted my machine a short while ago - as have all versions so far! Ah, well. I'll just wait it out. SSDD. This is what can happen with a new project, so we cannot moan too much.

Happy crunching!

---

> Thought it was ok, until it rebooted my machine a short while ago - as have
> all versions so far! Ah, well. I'll just wait it out. SSDD. This is what
> can happen with a new project, so we cannot moan too much.
>
> Happy crunching!

Do you overclock your machine?

It sounds like your processor is getting to hot.

---

----- Rom
BOINC Development Team, U.C. Berkeley
My Blog

Not at all. This is a pure crunching machine. Not used as anything else. As was from factory, except for security and Boinc, etc...

Have had this problem with every version. Temp is ok.


I cannot say with 100% certainty, but I am sure when I was last sat here earlier today, and had just had a look (crunching an Einstein Unit at that point) it suddenly rebooted. When it came back, it was crunching a seti unit. I wonder if the problem lies with the switch-over?

---

I'm not sure about that, there isn't anywhere in the codebase where a call to ExitWindows() is called.

The only times I've seen a machine reboot without being told too, is normally related to a hardware problem.

Generally a CPU or memory problem, although I have seen a disk controller cause a machine to reboot, but mostly bad disk controllers cause the blue screen of death.

---

----- Rom
BOINC Development Team, U.C. Berkeley
My Blog

for a win xp machine I would suggest looking in the event viewer
(control panel adminstrative tools) for any entry error logs.

(You may have the automatic restart on error options set.
control panel system advance startup & recovery)

Ok, there was a savedump, in fact a few, which would correspond with the reboots. The problem is beyond me at this time of night! 11.30pm. I am a postman, up in 4 1/2 hours!

And correct, the restart was checked for startup recovery problems. It just seems coincidental that the problems have only occured since starting Einstein.

But maybe I'm wrong.

I *will* check it out more thoroughly tomorrow. Hopefully (I don't wish) it is a problem at my end...

And thanks for the responses, BTW.

---

Sudden reboots are also often caused by a too weak power supply.
Especially the Einstein cruncher is very cpu intense. With Seti crunching my temps are ~45-46°C with Einstein the temps go up to ~49-50°C. Accordingly to the temps the cpu current is also raising a lot on my Athlon Thunderbird. Maybe the Einstein is too much for you power supply?

---

Aloha, Uli

i have updated both of my machines to boinc 4.19...so far no differences noted.

---

PROUD TO BE TFFE!

> Sudden reboots are also often caused by a too weak power supply.
> Especially the Einstein cruncher is very cpu intense. With Seti crunching my
> temps are ~45-46°C with Einstein the temps go up to ~49-50°C. Accordingly to
> the temps the cpu current is also raising a lot on my Athlon Thunderbird.
> Maybe the Einstein is too much for you power supply?
>
>
Uli,

You may be correct, but I can't see how Einstein could cause that much more heat than Seti, which on my machines runs over 99% cpu utilization. Maybe there's more disk activity?

---

<img src='http://www.boincsynergy.com/images/stats/comb-912.jpg'>

> You may be correct, but I can't see how Einstein could cause that much more
> heat than Seti, which on my machines runs over 99% cpu utilization. Maybe
> there's more disk activity?

Well, there is a lot of debate over what percentage of the CPU/FPU is being used. I will note that 3 projects are using FORTRAN as the language of choice to make the Science Application (LHC@Home, Einstein@Home, and CPDN).

For those that think that all languages are alike, well, my past experience is that a FORTRAN compiled application is far more efficient and accurate when doing heavy duty calculations. I doubt that there has been anything done on this end by the C compiler writers.

With that in mind, if the code is more effective in keeping more of the CPU busy, well, power consumed by the CPU is dependent on the number of transistors changing state. The more that are changing state, the higher the power consumption.

---

> With that in mind, if the code is more effective in keeping more of the CPU
> busy, well, power consumed by the CPU is dependent on the number of
> transistors changing state. The more that are changing state, the higher the
> power consumption.
>

That's right. The power consumption is very much dependent on wich sort of machine instructions are used by the compiler. I know of a very old cpu burn program for MSDOS that simply executed a "Jump 0" (i.e. a jump to itself) that was able to burn the old passive cooled 386 & 486'ers in five minutes.

Additionally you can see that the Seti cruncher, thanks to poor memory management in the code, generates *LOADS* of page faults leading to insert a wait cycle for transferring the missed page into the cache. Therefore the cpu (although 99.9% cpu usage) is idle a little. In contrast the Einstein cruncher generates nearly no page faults and uses the cpu much more effective, leading to a higher temperature and current usage.

---

Aloha, Uli

> That's right. The power consumption is very much dependent on wich sort of
> machine instructions are used by the compiler. I know of a very old cpu burn
> program for MSDOS that simply executed a "Jump 0" (i.e. a jump to itself) that
> was able to burn the old passive cooled 386 & 486'ers in five minutes.

Even better, I stole it Ulrich, thanks! :)

So, now we have a new FAQ topic on I am runnning BOINC on my laptop, why is it so hot?

---

> Even better, I stole it Ulrich, thanks! :)
>

You are very welcome, i feel honored ;)

---

Aloha, Uli

> You are very welcome, i feel honored ;)

as usual, I edited it a little ... did you look at it?

---

> as usual, I edited it a little ... did you look at it?
>

Yes i did, looks better that way. English is not my native language but i think i'm doing well ;)

---

Aloha, Uli