> Now, as for downloading too many workunits and the potential for workunit
> expiration, I believe there is a daily quota, and mine appears to be 16
> workunits downloaded per day. If I have the update frequency set to 1.0 days,
> I do not think I should exceed that quota. This is just about what I process
> in a day. So we should be fine there. I will give this a few days to see if I
> start queueing up.
The daily quota is per machine, not per user.
The worst problem with large caches at the moment is that each project will overfill its fraction of the cache, and deadlines will be missed on multiproject machines.
I've downloaded it and after configuring it correctly (took a while for GUI RPC), it works quite well on the local network. Thanks for the link--it's pretty cool. I will try this on the remote network machines as well to see if I can get them to report.
Cheers mate,
Mino
> I found it by sorting the messages for all computers with Boincview - which I
> consider a very good tool if you have more than just 1 or two machines
> running.
> You can get this tool here:
>
> http://boincview.amanheis.de/?page=download
Thanks for clearing that up. I prefer to focus energy on a single project at a time. So I am phasing out Seti@Home and transitioning all machines except for one to Einstein solely. I would yank SETI off the one machine too but I will lose cross-project credit linking, which is a drag...hopefully they will resolve this issue in a future release.
Cheers,
Mino
> The daily quota is per machine, not per user.
>
> The worst problem with large caches at the moment is that each project will
> overfill its fraction of the cache, and deadlines will be missed on
> multiproject machines.
> Now, as for downloading too
)
> Now, as for downloading too many workunits and the potential for workunit
> expiration, I believe there is a daily quota, and mine appears to be 16
> workunits downloaded per day. If I have the update frequency set to 1.0 days,
> I do not think I should exceed that quota. This is just about what I process
> in a day. So we should be fine there. I will give this a few days to see if I
> start queueing up.
The daily quota is per machine, not per user.
The worst problem with large caches at the moment is that each project will overfill its fraction of the cache, and deadlines will be missed on multiproject machines.
BOINC WIKI
I've downloaded it and after
)
I've downloaded it and after configuring it correctly (took a while for GUI RPC), it works quite well on the local network. Thanks for the link--it's pretty cool. I will try this on the remote network machines as well to see if I can get them to report.
Cheers mate,
Mino
> I found it by sorting the messages for all computers with Boincview - which I
> consider a very good tool if you have more than just 1 or two machines
> running.
> You can get this tool here:
>
> http://boincview.amanheis.de/?page=download
Hi John, Thanks for
)
Hi John,
Thanks for clearing that up. I prefer to focus energy on a single project at a time. So I am phasing out Seti@Home and transitioning all machines except for one to Einstein solely. I would yank SETI off the one machine too but I will lose cross-project credit linking, which is a drag...hopefully they will resolve this issue in a future release.
Cheers,
Mino
> The daily quota is per machine, not per user.
>
> The worst problem with large caches at the moment is that each project will
> overfill its fraction of the cache, and deadlines will be missed on
> multiproject machines.