If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.

I noticed that over the last 2 weeks that the memory requirement per task started increasing for this project.
I have also noticed that the CPU interrupts are not working very well -> the tasks are hogging the CPU and not handing back very well at all causing desktop lockups in Windows 7 x64.

The main issue of limited memory represents as WU-hang - work units that never finish - which has meant some baby sitting.
Check any of your machines that have around 1.5GB per core. 2GB per core should still be OK at time of writing.

The upshot is that after isolating my other projects from interruption and restricting work units to a suitable RAM-per-core I am suddenly down to 2 cores (2 separate dual core machines) on this project!

Yes agree with the memory hogging in this project Dave. On the official site there is an app_config.xml file posted that I use now on my 4GB RAM Win7 systems. It limits running tasls to 2 or 3 instead of 4. On a Xeon system of mine with 8GB when it was trying to run 8 threads the tasks were taking 12+ hours. After limiting the system to 7 tasks they now finish in 1-2 hours. This machine is still suffering slow downs so I might limit it to 6 or even 5 concurrent tasks.

I have one machine running 123numbers with 8Gb of RAM (4 cores) and another with 13Gb (6 cores), so far both seem to be ok but I hope they don't increase the memory requirements again or I may have to lower the number of cores for it, or switch to something else.

After a sabbatical from this project, I gave it another run.
100% invalid work unit results on Windows client and linux client.
As someone already pointed out elsewhere this project has ground to an almost complete halt with zero successful results from all users only days away and the admins are not doing anything about it.http://stats.free-dc.org/stats.php?page=proj&proj=vdw

The project admin recently broadcast a message out to existing members that a number of issues were fixed.
Testing so far reveals that the results are positive.
For the most part the validator itself was not the problem, it was memory allocation bugs in the clients causing mismatches in the result validation.
The good news is that the project has new clients and this time it is working as intended.
There are still some errors coming back from a few windoze machines but that is being monitored and assessed.
Otherwise all stations are GO!