I am quite curious as to the relative success rate of the Capri14 WUs versus WUs of all other types.

My personal experience is that a Capri14 WU is nearly doomed to failure, no matter the Rosetta version on which it is running, while nearly all other WUs will succeed...

I sincerely hope that the CPU time that (to my layman's perspective) I seem to be wasting on Capri14 is not representative of the experience of the general population of Rosetta crunchers.

Respectfully,
David Emigh

David I believe you are having a bad run of luck on the WUs. I also have had several fail but overall better than 95% have finished with valid results. Like a few others I have had to make adjustments to memory allocations on my old machines but the CAPRI14 project will soon be over and we can get back to the same old boring number crunching.
I also don't like the "client error" result either it does give me a since of loss.

Cheers Jim

David I believe you are having a bad run of luck on the WUs. I also have had several fail but overall better than 95% have finished with valid results. Like a few others I have had to make adjustments to memory allocations on my old machines but the CAPRI14 project will soon be over and we can get back to the same old boring number crunching.
I also don't like the "client error" result either it does give me a since of loss.

Cheers Jim

Thanks for responding, Jim. It's good to know that someone (anyone) is getting good results back on the Capri14 WUs.

I seriously doubt that there are memory allocation problems with my computer, as I have it loaded up with 4Gb of RAM, 50% of which is dedicated to BOINC. If that's not enough RAM for the Capri14 WUs, they have no business being run in a distributed computing project.

---

Rosie, Rosie, she's our gal,
If she can't do it, no one shall!

I've crunched a handful of CAPRI14 workunits on my P4 3.2Ghz w/HT and 1GB of RAM (511.62 MB available while in use, 920.91 MB when idle, according to BOINC Manager) and with applications set to be left in memory, without a single problem, on both 5.79 and 5.80 app versions.

---

I am quite curious as to the relative success rate of the Capri14 WUs versus WUs of all other types.

My personal experience is that a Capri14 WU is nearly doomed to failure, no matter the Rosetta version on which it is running, while nearly all other WUs will succeed...

I sincerely hope that the CPU time that (to my layman's perspective) I seem to be wasting on Capri14 is not representative of the experience of the general population of Rosetta crunchers.

Respectfully,
David Emigh

David I believe you are having a bad run of luck on the WUs. I also have had several fail but overall better than 95% have finished with valid results. Like a few others I have had to make adjustments to memory allocations on my old machines but the CAPRI14 project will soon be over and we can get back to the same old boring number crunching.
I also don't like the "client error" result either it does give me a since of loss.

Cheers Jim

It seems that only a few types of WUs will result in some sort of failure. Most have given me a success. I don't really see it as wasted CPU time but then credit should be allocated accordingly for the results.

---

BBLounge - Broadband and Technology forum

I'm free thinking here but is it possibel that memory cach size come into play here?

Anders n

Hmm, it seems the only people with problems here have two or more CPUs. The only one without problems is Anonymous here but he hasn't been running a lot of these WUs and not for long. Maybe a cache inconsistency between processors? This is strange since a WU is usually only run on one processor at a time but my cpu usage sometimes goes well above 50% on one and well below on the other.

---

BBLounge - Broadband and Technology forum

Another 1g4u aborted that got stuck. As suspected it was using between 50~60% cpu.

---

BBLounge - Broadband and Technology forum

Hmm, it seems the only people with problems here have two or more CPUs. The only one without problems is Anonymous here but he hasn't been running a lot of these WUs and not for long. Maybe a cache inconsistency between processors? This is strange since a WU is usually only run on one processor at a time but my cpu usage sometimes goes well above 50% on one and well below on the other.

I've only seen it exceed 50% when I'm running the graphic. Since this runs in a seperate thread, it exceeds 50% when combined with the crunching thread.

---

Rosetta Moderator: Mod.Sense

1g4u__BOINC_CAPRI14_DOCK_FIXBACKBONE-1g4u_-nodimerloop_plexinmonomer__2067_505 ... stuck ...

---

BBLounge - Broadband and Technology forum

See this post for the current status of Capri14 workunits.

---

Rosie, Rosie, she's our gal,
If she can't do it, no one shall!

i got one capri after reseting and redoing rosie's program.
i thought capri was purged?

See this post for the current status of Capri14 workunits.

---

I just got another Capri14 this morning that some had aborted, i thought

they were finished. No problem though, i'll let it run.

Pete.

---

What ends up happening is, even though they purge a given task type from the queue... over time, tasks that have been issued to others miss deadlines or fail and are then automatically reassigned to machines requesting work. So purging the queue is a good first step, but it doesn't clear out 100% of the problem tasks.

---

Rosetta Moderator: Mod.Sense

Thank you, Mod.Sense, that was a point of concern for me also :-)

---

Rosie, Rosie, she's our gal,
If she can't do it, no one shall!

ahh! that explains why i got one after i upgraded

Thank you, Mod.Sense, that was a point of concern for me also :-)

---

Well it got stuck like a lot of the others, there you go!

https://boinc.bakerlab.org/rosetta/workunit.php?wuid=95275260

Pete.

---