Hello just to clarify a few issues. We'll get it all working first and then look at any memory and other optimisations.
As to the GUI you can close it. Once we've got the basics working I'll add an option and if the general consensus is to have it off, to make that the default. However that applet will only consume resources when repainted (it is designed not to repaint by itself, only when you resize it or reshow it, etc..).
As to "work being done". Yes all of your connections are generating useful work. Basically if your client is showing up here http://www.dhep.ga/statstopology.php
then it's connected OK. NOTE: at the moment all Windows clients are showing up as WinBoinc as we are yet to make our custom build of the wrapper (eventually will aim to add these enhancements to the main BOINC branch).
A quick brief of how this project will be working with BOINC:
- o A GA is an indefinite process so tasks will be set to have long lengths. A GA will work best with stable islands however feel free to pop in and out if necessary. Work is submitted to the server every 15 minutes.
o Credit will be assigned via the trickle system.
o Task files sent out are dummys - the actual work is downloaded from our servers - and as progress is submitted to our servers every 15 minutes - there is no output to validate. If your client has run the GA and sent progress updates that is already enough.
For now you can have an idea of your client's throughput here: http://www.dhep.ga/statsdailyrankings.php
We'll first focus on credit assignment, then on tidying up the input/output of workunits, and then some Windows customisations and performance.
As to memory/performance, we've had 144 VMs running on two (large) hosts continuously for 3 weeks now with no issues. But we'll address these on a case by case basis (I suspect mostly Windows) when the time comes.