TRNG98,

There is a minimum memory requirement as not all of our members have machines that are dedicated to crunching. Meaning they are their every day machine to check email and surf the internet. World Community Grid strives to be a low impact on a member's machine as possible.

The minimum Requirements listed on the site are what we recommend for a computer and OS installed on the machine. This is because the default BOINC settings is to use something along the lines of 75% of available memory of the computer. Thus the limit you'll see when downloading a work unit from BOINC is closer to 250MB of available RAM.

You can change your memory usage on your machines to be 100% if you'd like through the BOINC client. This is done by editing your preferences.

Work units for VINA are very intensive with the memory it uses. This means if it allocates 50MB of memory to use during it's run, ALL 50MB is used and none is allowed to go into paging. This causes other processes that are less memory intensive (but still allocate space) to send things to cache (swap space). This will cause those applications to seem sluggish or slow when attempting to use them.

Also, if you don't mind me asking, what is the memory of these older machines?

Hope this helps explain the memory requirement.
-Uplinger

As you say you do NOT want to run anything else but WCG on these machines, then just do it. Uplinger says that 50 Megs is used by WCG so as you have 191 then it should run ok....

TRN98,

Assuming you read the earlier thread in GFAM forum on System requirements and actual use, you'd seen that the *running* values are about 30-35MB and similar amount in VM. Just specify the required amount that WCG tests for, being 250MB, even though it may not be used, but could be used. Whether 250 is free is not important, but what's specified and what's physically there, logged at start of client, is. If it's less you get this:

1310 WCG 15-11-2011 09:41 Beta - Drug Search for Leishmaniasis needs 384.00 MB RAM but only 184.16 MB is available for use.
1311 WCG 15-11-2011 09:41 Beta Test - GO Fight Against Malaria needs 384.00 MB RAM but only 184.16 MB is available for use.
1312 WCG 15-11-2011 09:41 GO Fight Against Malaria needs 250.00 MB RAM but only 184.16 MB is available for use.
1313 WCG 15-11-2011 09:41 No work available for the applications you have selected. Please check your settings on the website.

We've seen this with the same science engine driven DSFL where suddenly a batch came by that *used* > 220MB of RAM. If these get to your 191MB machines, things start moving like molasses, as Uplinger explained, but if these machines arrent doing anything else, what's *your* worry? WCG's worry is the individual volunteer, it being *impossible* to specify requirements on a specific volunteer basis, so the SRs are set for *worst case*.

You can do the JDI and run with it and hope none come to you that have actual need of the full search box that is allowed to grow to 250MB at any time, without notice. You take that risk consciously. Start 1, look in properties, and presently you see this:



Each time you've got you nodes available, run a brief test, then open the gauges, that is of course if you're willing to spend a little time doing that.

All *free* CPU time is much appreciated, but the prime premise is that it does not impact the user of the computer(s)... almost like the 3 laws of robotics... impediment is harm... harm is loss of volunteer.

--//--

There's no need to assume a shouting tone by posting enlarged and bolded text in a regular forum post. That it bugs you that WCG wont buckle is clear without.

1. The error you saw in my log of 184Mb is what I *forced*, by setting the allowed to 9% of 2GB. Yes you can set all 256 in a client preference and the servers will accept that if physically there... I did not say or infer anything else. If I set it to 100%, my client reports this:

1418 15-11-2011 13:59 max memory usage when active: 2046.18MB
1419 15-11-2011 13:59 max memory usage when idle: 2046.18MB

i.e. it is not considering that part of the memory has already been used by the OS et cetera.

2. There cant be a compromise on the RAM spec as Uplinger and I did note that the instances do come around where > 220MB was used i.e. the individual being impacted if borderline devices were to receive these.

Now, what device has 191 *physical*? 3 banks of 64K minus some overhead? In that case, that's than how it is. Do WCG jeopardize the whole for the one by removing or lowering the limit? Don't think that will be and doubt they'd be reconsidering. Testing on a *per result* or *per batch* basis to see if it fits a device is not an option. WCG has 10 projects running on multiple platforms. As it is, a serious support effort.

--//--

etienne06,

Suspect to have the answer for you why you got the image files, but not any WU. I'll let the techs though answer as being opted in will, it seems, always download the permanent/persistent files for a project even if a device does not meet the requirements. The why is unknown to me.

--//--