...
Mike,
Thanks very much for taking the time to do all that.
I used BOINCView extensively when my farm had about 20 or so machines. By the time the number had reached about 30-40, the machine on which the app was running was brought to its knees and the app started locking up at regular intervals. I had to abandon BOINCView. Maybe there are now more recent versions which scale better.
...
in an older version of BOINCView I noticed a memory leak.
BV was collecting more and more memory. I had to stop it on fridays otherwise on mondays my 'central BV computer' was unresponsible due to large memory allocations by BV. So I also abandoned BV.
In November I tried BV again and the memory leak is fixed now!
Now I'm using BV version 1.2.6 (but only with 4 hosts).
Interesting idea -- thanks for making the suggestion. For my setup, there are a couple of negatives I can think of.
*Cache size. This would need to be increased to cover the possibility that contact might not be able to be established in the small daily window of opportunity.
*Backup projects. My guess is that these would be a lot harder to manage than currently is the case. Particularly since LHC is my strongly preferred backup from which I very much like to grab work when it is available.
*Spotting misbehaving machines. My current strategy (explained in a previous post) would probably not work as well.
*Bandwidth saturation. Imagine 200 machines all trying to get new work and perhaps many trying to download new 15.7MB data files all in that single window of opportunity.
Actually, on balance, I think I'll stick with the devil I know :).
But many thanks for the suggestion anyway.
I will try it out. From now on my machines connect only between 16°° and 17°° UTC. There is one C2D which crunches 90+ small units a day, so this one seems to be the critical one as long as it gets a majority of small units.
Hopefully I do not get a chance to test this change ...
But I agree that you may get problems with the bandwidth when 200 boxes connact at the same time. Well, you can use 3 profiles having different access times, but with 66 boxes on each profile there may arise similar problems.
And I have no real idea how boinc behaves with different settings for different projects ... at least a few settings (like the cache size/connect to network about every ...) seem to be specific for one project and do not apply to all.
And I have no real idea how boinc behaves with different settings for different projects ... at least a few settings (like the cache size/connect to network about every ...) seem to be specific for one project and do not apply to all.
Those are general preferences; they should get synchronized among projects as each is updated. But when you’re using separate venues things get more interesting; it seems that a given host can belong to different venues on different projects, in which case it can have varying preferences. I’m not sure how BOINC sorts that out.
A note on RealVNC- the free version. It does not allow password encryption. You can get around the security issues by setting the remote host firewall to reject all unknown connections to the ports it uses (I think 5801{HTTP} and 5901{VNC} if I recall right).
I said, it had 'password lockout'. The newer free version DOES have password lockout\\authentication. (And this newer version that I have, has been around for over a year I believe) Works good for me. :D
RE: ... Mike, Thanks very
)
in an older version of BOINCView I noticed a memory leak.
BV was collecting more and more memory. I had to stop it on fridays otherwise on mondays my 'central BV computer' was unresponsible due to large memory allocations by BV. So I also abandoned BV.
In November I tried BV again and the memory leak is fixed now!
Now I'm using BV version 1.2.6 (but only with 4 hosts).
Udo
RE: Interesting idea --
)
I will try it out. From now on my machines connect only between 16°° and 17°° UTC. There is one C2D which crunches 90+ small units a day, so this one seems to be the critical one as long as it gets a majority of small units.
Hopefully I do not get a chance to test this change ...
But I agree that you may get problems with the bandwidth when 200 boxes connact at the same time. Well, you can use 3 profiles having different access times, but with 66 boxes on each profile there may arise similar problems.
And I have no real idea how boinc behaves with different settings for different projects ... at least a few settings (like the cache size/connect to network about every ...) seem to be specific for one project and do not apply to all.
RE: And I have no real idea
)
Those are general preferences; they should get synchronized among projects as each is updated. But when you’re using separate venues things get more interesting; it seems that a given host can belong to different venues on different projects, in which case it can have varying preferences. I’m not sure how BOINC sorts that out.
IIRC, it's like all the other
)
IIRC, it's like all the other Global prefs, it will take the venue set on the most recently updated project.
Alinator
RE: A note on RealVNC- the
)
I said, it had 'password lockout'. The newer free version DOES have password lockout\\authentication. (And this newer version that I have, has been around for over a year I believe) Works good for me. :D
d3xt3r.net