Jose, How many puters do you really have? I see six IDENTICAL puters in your account and the benchmarks are all over the map.

1) Measured floating point speed 2009.88 million ops/sec
Measured integer speed 4014.11 million ops/sec

2) Measured floating point speed 2012.98 million ops/sec
Measured integer speed 4045.58 million ops/sec

3) Measured floating point speed 545.31 million ops/sec
Measured integer speed 3966.71 million ops/sec

4) Measured floating point speed 1276.07 million ops/sec
Measured integer speed 5114.47 million ops/sec

5) Measured floating point speed 1986.21 million ops/sec
Measured integer speed 3371.27 million ops/sec

6) Measured floating point speed 1154.1 million ops/sec
Measured integer speed 235.34 million ops/sec

If you just have one machine continuously being attached/detached then you have a issue here.

Note: none of this conversation belongs in this thread, maybe a mod could move them.

I have only one. The other 5 are "ghosts" that could be corrected if the BOINC Merge function were in place, but it is not.

But that will not longer be a problem. See, I just got tired of checking and rechecking and calling the people that help me ( at a cost to me) my computers, etc , etc. This is highly inefficient. It goes against my nature. It makes feel useless . All the hassles have actually robed the joy of participating from me.

I am exhausted. I am tired

I just give up.

Exeunt

Jose

---

This and no other is the root from which a Tyrant springs; when he first appears he is a protector.”
Plato

No probs, easily done and nobody got killed. ;-} :thumbsup:

---

I am exhausted. I am tired

I just give up.

Exeunt

Jose

No doubt about it, hardware problems are a bitch! Maybe if you know someone nearby to you who is one of those "computer gurus", they might be able to provide a fresh perspective? The folks that are whizzes can sometimes (but not always!) provide solutions not considered. And they are there on the spot, hands-on, which I found can be very helpful because long-distance help although very well intentioned is no substitute for someone having their hands directly on the machine. Just a thought! :)

---

Regards,
Bob P.

Are you saying that the CPU time is not increasing, even though it's "running"? Is the idle process getting all the CPU time when this WU is "running"?
............
Is there anything in the messages around the time that this WU stopped?

Exactly, the cpu time is not increasing.

I will check the messages.

---

..................

First of all I would exit BOINC and restart and see if the WU "revives". If that isn't the case I'd abort it.

I can't exit Boinc immediately because my machine is running also uFluids@home.
This application has no checkpoint. I have began a wu "zerobubble" and after 7h 34 min of cpu time, the % done is at 39 %.
So i need to wait.

For now i suspended my wu Rosetta.

---

possible problem as im boggled why this is happening but recently on WU's that take like 10,000+ seconds meaning its like 10,000-10,700 or something like thati used to get 92 credit points for em now im only getting 72/71?? what gives..

https://boinc.bakerlab.org/rosetta/results.php?hostid=210073

^^ thats the comp look at like last 10 results

---

possible problem as im boggled why this is happening but recently on WU's that take like 10,000+ seconds meaning its like 10,000-10,700 or something like thati used to get 92 credit points for em now im only getting 72/71?? what gives..

https://boinc.bakerlab.org/rosetta/results.php?hostid=210073

^^ thats the comp look at like last 10 results

here's your benchmarks:

Measured floating point speed 3024.34 million ops/sec
Measured integer speed 9085.53 million ops/sec


Here's the formula for "claimed credit"

claimed credit = ([whetstone]+[dhrystone]) * wu_cpu_time_in_sec / 1728000

From this I can only assume you recently reran the benchmarks and they came out lower. The benchmarks run each time you install a new boinc client, and then every 5 days after that.

tony
you can manually rerun the benchmark as well.

---

My 24hr WUs (86,000 seconds) seem to range from 120-220 credits. The good news is that in my case there's not sudden marked decline with new versions or anything, it's just not a very accurate thing.

---

Add this signature to your EMail:
Running Microsoft's "System Idle Process" will never help cure cancer, AIDS nor Alzheimer's. But running Rosetta@home just might!
https://boinc.bakerlab.org/rosetta/

possible problem as im boggled why this is happening but recently on WU's that take like 10,000+ seconds meaning its like 10,000-10,700 or something like thati used to get 92 credit points for em now im only getting 72/71?? what gives..

https://boinc.bakerlab.org/rosetta/results.php?hostid=210073

^^ thats the comp look at like last 10 results

here's your benchmarks:

Measured floating point speed 3024.34 million ops/sec
Measured integer speed 9085.53 million ops/sec


Here's the formula for "claimed credit"

claimed credit = ([whetstone]+[dhrystone]) * wu_cpu_time_in_sec / 1728000

From this I can only assume you recently reran the benchmarks and they came out lower. The benchmarks run each time you install a new boinc client, and then every 5 days after that.

tony
you can manually rerun the benchmark as well.

yea dude didnt even realize that :[ just reran the benchmark cause i had oc'd the cpu back up again and my measured floating pt speed just jumped back up to 3779 :]

---

I still keep getting units that say they are running when they are not. No Error messages in the log.

---

I still keep getting units that say they are running when they are not. No Error messages in the log.

Go to the Projects tab, look at rosetta, then follow that line over to the "Status" column. does it say "suspended" there? You should also check
the work/tasks tab to see if that particular WU is suspended.
Is rosetta your only project? If not, then are the other projects working OK?
If Rosetta is your only project, right click on the B in the systray and see if Boinc is suspended, or set to do work based on prefs.
If set on based on prefs, then check you "general preferences" under "your account" and see if you have asked it to stop work while in use, or at specific times.

tony

I suspended the work unit after I noticed it wasn't consuming any CPU time, I don't have time to baby sit it right now. Seti and Predictor are also running on this machine and have no problems. Roseeta seems to have this problem every few work units. It used to be worse before 5.07.

---

I still keep getting units that say they are running when they are not. No Error messages in the log.

I just reread your post. Do you mean it says "running" in the status column of the work/tasks tab? If yes, have you viewed the graphics to see if they're running. Are you a Win98/me user?

[edit]I see two linux and one win2000 puter, which puter?

This is a linux machine I don't run the graphics on it, and so have no I dea what they would look like. The siutation was definitly that the status of the Work unit was running and that no CPU was being consumed. When the Work units get in this state they hog all the computer time without accomplishing anything.

---

This is a linux machine I don't run the graphics on it, and so have no I dea what they would look like. The siutation was definitly that the status of the Work unit was running and that no CPU was being consumed. When the Work units get in this state they hog all the computer time without accomplishing anything.

If you can restart BOINC. If there is still no CPU usage abort. You get credit and the WU will be sent out to someone else.

---

This is a linux machine I don't run the graphics on it, and so have no I dea what they would look like. The siutation was definitly that the status of the Work unit was running and that no CPU was being consumed. When the Work units get in this state they hog all the computer time without accomplishing anything.

Can you do a "ps" to see the status of the BOINC and Rosetta processes? Or use "top" to see if it consumes CPU time?

E.g. on my Linux (notice the STAT column, RN=Running, Nice):

ps u -U boinc
USER       PID %CPU %MEM   VSZ  RSS TTY      STAT START   TIME COMMAND
boinc     2120  0.0  0.4  7396 3684 ?        S    Apr27   0:06 ./boinc_client
boinc     8605 21.8  8.5 158868 63416 ?      RN   May02 404:22 rosetta_5.07_i686
boinc     8606  0.0  8.5 158868 63416 ?      SN   May02   0:00 rosetta_5.07_i686
boinc     8607  0.0  8.5 158868 63416 ?      SN   May02   0:00 rosetta_5.07_i686
boinc     8608  0.0  8.5 158868 63416 ?      SN   May02   0:00 rosetta_5.07_i686

I had a similar problem with yours 3+ months ago, on a under-spec'ed Linux where I was running 6 different BOINC projects with leave-preempted-in-mem=Yes on a PC with just 256MB RAM, where BOINC would think Rosetta was running, but it didn't. So BOINC wouldn't switch between projects, effectively "hanging".

I never looked into it, I just reduced # of BOINC projects to 3 and I've never had the problem again.

---

Best UFO Resources
Wikipedia R@h
How-To: Join Distributed Computing projects that benefit humanity

---

OS = Linux 2.6.10
CPU = AMD Sempron 3000+
Memory = 1024M (64M shared video)

Failure Rate: approximately 70%

With v5.01 of the Rosetta app, this rig ran clean. Near 100% completion.
With v5.07, I'm lucky to get 1 result in 3 successfully completed.

Any suggestions?