| Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
| World Community Grid Forums
|
| No member browsing this thread |
|
Thread Status: Active Total posts in this thread: 5
|
|
| Author |
|
|
shanen
Cruncher Joined: Nov 17, 2004 Post Count: 27 Status: Offline Project Badges:
|
I guess it's just a feedback post, since I don't really expect any of the current problems I'm mentioning to be fixed, which is another kind of negative feedback. Actually, it seems like some of the problems eventually do go away (with the notable exception of the dead team problem), so it doesn't really matter much. I even think the low-key approach is fundamentally better from a scientific perspective.
The main feedback of this post is to note that the Linux client seems quite flaky these days and is creating a rather negative impression, at least for this particular user. Lots of (long-term and recurring) problems with server access at your end, but even when the servers can be accessed, they often decide that there is no suitable work available for various Ubuntu machines. Other times they send work units that are too large to be completed within the deadline on the usual operating schedule of the particular machine. That should be avoidable by checking to logs, I would think... (That problem often bothers my Windows computers, too.) Even worse than that is the newest symptom, in which a server decides there is some suitable work available, the work is downloaded and started, and then the client freezes at this end with a 'waiting for memory' message. Plenty of swap available, but it probably needs real RAM and it judged the problem size inappropriately. My employer only officially sanctions this particular project, but it often seems like it would be less trouble to switch to some of the other BOINC projects... I played with a couple of them when I was first learning Ubuntu stuff, and most of them seemed to create a rather more favorable impression than this one. |
||
|
|
Sekerob
Ace Cruncher Joined: Jul 24, 2005 Post Count: 20043 Status: Offline |
Hi shanen,
----------------------------------------this post would have had a better fit in the BOINC support forum. On read all of the sighted problems seem relatively easily fixable with same preference changes and some setup verification. If interested in actually resolving, wait a bit and Didactylos will come around. Meantime, try changing your My Grid > Device Manager > Device Profile > Profile of Choice to Maximum Output and Update the Project connection. That will make enough RAM available for any job on a >= 256mb RAM machine. Also tell us the BOINC version, source you got it from and post the actual message from the message tab. cheers
WCG
----------------------------------------Please help to make the Forums an enjoyable experience for All! [Edit 1 times, last edit by Sekerob at Aug 14, 2007 9:09:25 AM] |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
shanen, if you want things to be fixed, you will have to be specific.
I see you have already upgraded to the 5.10 BOINC client. That action may have been premature - the client isn't officially recommended by WCG yet. As for the majority of your problems - I believe they were caused by the recent FAAH upgrade, which (by design) caused some unusual deadlines and a brief period of work unavailability. The upgrade is now complete, and you shouldn't see so many problems. The memory problem we can solve. BOINC 5.10 has a new memory preference, and it defaults to 50% when your computer is in use - obviously, that's not going to work on a memory-constrained computer. To fix it, go to your device profile as Sekerob said. But set it to "custom", check that memory use is set to 100%, then save the profile, even if it was already at 100%. Then update BOINC. Doing this adds the new preference to your settings, and will override the BOINC default. The normal deadline for most WCG work is 9 days. Late work is accepted, but still - 9 days should be enough for any reasonable computer. If a particular computer frequently misses deadlines, you need to decide whether it is doing any worthwhile work. |
||
|
|
shanen
Cruncher Joined: Nov 17, 2004 Post Count: 27 Status: Offline Project Badges:
|
Thanks for the detailed reply, and sorry for my slow follow-up I had found a way to evade the problem until this week. However, upon my return here, I followed your instructions, and found that it was already set for a custom profile and 100% memory per your instructions. I don't remember when I did it, but there it was. I was unsure about the next step, but I guess you mean to reset the project, so I did that again, too. It looks like this machine is just useless for WCG. The physical RAM is only 192 MB on this one, and it's only a scratch monkey that can't justify an upgrade.
I feel a bit like laughing that to hear that less than 256 MB of RAM is now regarded as a resource-constrained computer. My first personal box had all of 64 KB of RAM to run and play with. It seems pointless, but I may later post more details in the appropriate location (BOINC Support) that was mentioned earlier. Basically, the problem reached the critical level after my upgrade to Ubuntu Gutsy 7.10, and I think my only option is to switch to other BOINC projects that can deal with such miserably small computers. |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Sounds about right.
Remember, the software we are running was designed to run on supercomputers. The WCG technicians have done miracles in reducing the requirements, but resources are still needed. Another BOINC project, CPDN, has work units that require 5 Gigabytes of memory. We don't live in a 64 KB world any more. |
||
|
|
|