1) Message boards : Number crunching : my client will never connect (Message 18147)
Posted 14 Oct 2007 by Danish Dynamite
Post:
Try modifying your general preferences so that you don't connect more then .1 times per day. I think if you don't stretch out your connections you will not get work for the moment.

same thing for 12 hours:

10/14/2007 11:20:06 AM|lhcathome|Message from server: Not sending work - last request too recent: 66 sec
...
10/14/2007 11:23:13 AM|lhcathome|Message from server: Not sending work - last request too recent: 122 sec

its always too recent, no matter what




you need to get your client(s) to not request more work for an hour ie 3600 seconds easiest way would be to disable network activity
2) Message boards : Number crunching : Wait for it (Message 17112)
Posted 26 Jun 2007 by Danish Dynamite
Post:
Excellent. Thanks Alex and Neasan.

All we need now is some work.


ditto lol
3) Message boards : Number crunching : Past Due Date (Message 16035)
Posted 4 Jan 2007 by Danish Dynamite
Post:
Does this mean then that 2 people could be wasting their computer time for each work unit?

that is what i am thinking
4) Message boards : Number crunching : Past Due Date (Message 16028)
Posted 4 Jan 2007 by Danish Dynamite
Post:

There is a plan to have BOINC server notify the client when a quorum is reached so it can abort the workunit.


wont that mean if your comp is to slow you wont get any credits if result isnt obtain before a quorom is reached ?


only if You grab to many wu :p


lets assume that these 5 comps say intel celery 700mhz, athlon 1500+, intel core 2 duo, intel xeon, amd 64x2 5200+ all are running same version bonic client, os and are all only crunching in one project and all have Connect to network about every 0.1 days ect ect ie all comps are the same except for cpu processing power (yes i know these many more differences ie cache size,ram speed ide vs sta ect ect but work with me here please)

so in the above example the intel celery 700mhz and athlon 1500+ would never be able to return a work unit before a quorom of 3 has been reached ?? is this not correct or is my logic broken ??
5) Message boards : Number crunching : Past Due Date (Message 16024)
Posted 4 Jan 2007 by Danish Dynamite
Post:

There is a plan to have BOINC server notify the client when a quorum is reached so it can abort the workunit.


wont that mean if your comp is to slow you wont get any credits if result isnt obtain before a quorom is reached ?



©2024 CERN