| Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
 |
World Community Grid Forums
Category: Support
Forum: BOINC Agent Support
Thread: Minimum Project Requirements |
| No member browsing this thread |
|
Thread Status: Active Total posts in this thread: 7
|
|
| Author |
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Today I compared what I am finding running WUs to the given Minimum Specs for Projects, and there appears to be a massive difference.
----------------------------------------C4CW - 400Mb, current WUs running with 80Mb CEP2 - 1Gb, current WUs running with 80-90Mb They cant be system needs as other project specs at 250Mb/WU are below whats needed for the O/S alone, so must be the additional load to run them. Yet the reality seems way way lower. What I am missing? It doesnt look like they take drastically more at different stages of the crunching cycle, as my running figures apply to small percentage done up to 90% done. Just being cautious of getting caught by an aspect I am not aware of, because at present the min specs look to be way over the top. Regards Zy [Edit 1 times, last edit by Former Member at Nov 12, 2010 6:27:04 PM] |
||
|
|
Sekerob
Ace Cruncher Joined: Jul 24, 2005 Post Count: 20043 Status: Offline |
Zy,
----------------------------------------These requirements FAIU do not reflect the real usages. The line at the top says: "What are the recommended minimum system specifications?" Set the BOINC memory and free disk space limits to less than those in the SR table and you're likely not be receiving the relevant tasks (I've tested CEP2 and the message log printed a reason for denial). It's WCGs way to make sure that borderline devices do not run projects that can result in user negative experience.
WCG
Please help to make the Forums an enjoyable experience for All! |
||
|
|
kskjold
Senior Cruncher Norway Joined: May 20, 2008 Post Count: 469 Status: Offline Project Badges: 
|
Is it possible to override the minimum requirements?
---------------------------------------- |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Woa - just discovered why :)
----------------------------------------CEP2 WUs have lept to 145Mb each and still climbing, so on a hex core machine thats a tasty number for 6 of them - come back min spec all is forgiven  Edit: Looks like they are peaking at 195Mb each, and with them on a staggered start on each core, they will come inside the 1Gb spec on total peak use .... just :) So looks like 1Gb was a good call, could even argue its conservative number for a hex machine. Regards Zy [Edit 1 times, last edit by Former Member at Nov 12, 2010 9:14:32 PM] |
||
|
|
Ingleside
Veteran Cruncher Norway Joined: Nov 19, 2005 Post Count: 974 Status: Offline Project Badges:
|
Is it possible to override the minimum requirements? Not meeting the minimum "recommended" requirements isn't a problem, since these is often less than the actual limits. Example for CEP2 the actual memory-limit is 750 MB, and not 1 GB. Not meeting the actual task-limits on the other hand can't be overridden, since the Scheduling-server always checks if meets both disk- and memory-requirements of a task before you've assigned the task. For both disk-limit and memory-limit the scheduling-server uses your preference-settings, so depending on the limit you're not meeting it's possible changing preferences can help. But, since there's no way to set memory-limit to more than 100%, a computer with only 512 MB installed will never be assigned a 750 MB-task. A computer with 768 MB installed on the other hand can increase to 99%, and therefore get a 750 MB-task. As for client-side, the disk-limit is a "hard" limit, and any task violating the disk-limit will be aborted by client. For the memory-limit on the other hand, client uses your preference-setting, and will only abort a task if memory-usage is more than your preference-setting. This means, if a task is specified at 750 MB, and preference is 1.25 GB, you can happily use 1.1 GB memory (violating the task-limit), but if a task uses 1.26 GB memory it will be aborted by client.  "I make so many mistakes. But then just think of all the mistakes I don't make, although I might." |
||
|
|
Coleslaw
Veteran Cruncher USA Joined: Mar 29, 2007 Post Count: 1343 Status: Offline Project Badges: 
|
Nice to see you made it over to WCG Zy. Welcome.
----------------------------------------    |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
tyty :)
----------------------------------------Have to admit, the only reason I got here in the first place, was to get ready to help my BOINC team on the challenge starting 16th Nov..... Then, having got here I discovered, for the first time, what WCG was really all about properly, having to focus to get ready for the Challenge - and dang it, you guys have got me hooked I like the setup a lot and will be good to put the CPUs to use for a tangible end as opposed to some BOINC projects which are fine, but I sometimes wonder why I do it with them (except two - Aqua, thats a neat one working on future Quantum Computer design with a Private Sector Company thats actually developing one; and a good GPU one is GPUGRID - medical/scientific research based on molecular modelling). Not so here, many worthwhile end goals with a good choice to choose from. Plaudits to Admins/Staff et al, nice job  Regards Zy [Edit 1 times, last edit by Former Member at Nov 13, 2010 5:20:53 AM] |
||
|
|
|