I prefer a short turnaround time, it discourages the wu hoarders that slow everything down.
Yep. If i am in your seat this is how i would feel.
But i am in a seat behind old, slow crunchers on dial-up that want to play.
We know we slow things down, but rationalize that we add flops to the project.
At first start of this project wu’s were way smaller and took a short time to complete. To ease load on the server it was agreed to make wu’s have a longer process time. I must keep a close eye on Einstein since that decision.
If Bruce Allen feels confident now that the servers can handle extra pain i believe it and will do my part to put him to the test. I think i will find this project easier to run now and will hopefully no longer return a result 10 minutes past due because i decided to eat first after work instead of running to puter and dialing in.
The hoarders and slow-pokes will only slow this project down by a small fraction of it's lifespan and could in the long run help.
The 14 day turnaround might attract a batch of disgruntled folks out of SETI BOINC (or even SETI Classic), as SETI BOINC is going through a fair amount of pain with an excessive and growing Waiting For Validation queue.
I know that I started shifting CPU cycles to Einstein from both my SETI classic and SETI BOINC systems starting back in June in response to the ongoing litany of issues that SETI BOINC has been enduring.
Over the past 30 days, Einstein has gotten something like 56% of my CPU cycles, with SETI seeing 29% and Climate getting 15%
A month ago, the split was 60% SETI and 40% Einstein, and for the month of June it was 71% SETI and 29% Einstein.
At some point I might change the resource shares to increase SETI back up, but at this point, quite frankly, that project, based on the past two to three months, will need to EARN a higher resource share by demonstrating a higher level of stability, reliabilty and overall performance.
I expected a whole new package but it seems that only a config file expands the existing package from 7 day wu's to 14 day wu's. Is there an explaination anywhere?
One of the effects for me is that I am not running into 'overdues' as I was previously on some of my workstations -- especially those with shares with other projects in the mix. So for me, I 'stress' the systems here less as I no longer have to do 'resets'.
i'm happy about the new 14 day deadline...because that synchs E@H up with now i can finally use the recommended BOINC 4.45 client...because now the client doesn't think i'm way behind on before...the einstein WU's always had the earliest deadline...so rarely was a seti unit crunched...now all is just fine.
i'm happy about the new 14 day deadline...because that synchs E@H up with S@H
Good point. It does make things less complicated.
Quote:
so now i can finally use the recommended BOINC 4.45 client...because now the client doesn't think i'm way behind on before...the einstein WU's always had the earliest deadline...so rarely was a seti unit crunched...now all is just fine.
If you’re saying you’ve been running 4.19 until now I think you will really like 4.45
After a couple of weeks running 4.45 you should be able to sit back and see BOINC almost always make all the right decisions based on your prefs.
I’m surprised that 4.45 didn’t work for you with the shorter deadline because for me it made running E@H way easier. After crunching continuous E@H wu’s no new E@H wu’s were downloaded until other projects caught up to their share. My problem was that the next round of E@H sometimes hit me with 1 wu more than I could process before deadline. Underestimated completion time was the root problem. Big concern that may already be solved.
i'm happy about the new 14 day deadline...because that synchs E@H up with S@H
Good point. It does make things less complicated.
Quote:
so now i can finally use the recommended BOINC 4.45 client...because now the client doesn't think i'm way behind on before...the einstein WU's always had the earliest deadline...so rarely was a seti unit crunched...now all is just fine.
If you’re saying you’ve been running 4.19 until now I think you will really like 4.45
After a couple of weeks running 4.45 you should be able to sit back and see BOINC almost always make all the right decisions based on your prefs.
I’m surprised that 4.45 didn’t work for you with the shorter deadline because for me it made running E@H way easier. After crunching continuous E@H wu’s no new E@H wu’s were downloaded until other projects caught up to their share. My problem was that the next round of E@H sometimes hit me with 1 wu more than I could process before deadline. Underestimated completion time was the root problem. Big concern that may already be solved.
i'm already seeing 4.45 perform well...i was using Boinc 4.25 and had no problems before i upgraded...but 4.45 has more features...i think i'm gonna like it.
RE: I prefer a short
)
Yep. If i am in your seat this is how i would feel.
But i am in a seat behind old, slow crunchers on dial-up that want to play.
We know we slow things down, but rationalize that we add flops to the project.
At first start of this project wu’s were way smaller and took a short time to complete. To ease load on the server it was agreed to make wu’s have a longer process time. I must keep a close eye on Einstein since that decision.
If Bruce Allen feels confident now that the servers can handle extra pain i believe it and will do my part to put him to the test. I think i will find this project easier to run now and will hopefully no longer return a result 10 minutes past due because i decided to eat first after work instead of running to puter and dialing in.
The hoarders and slow-pokes will only slow this project down by a small fraction of it's lifespan and could in the long run help.
The 14 day turnaround might
)
The 14 day turnaround might attract a batch of disgruntled folks out of SETI BOINC (or even SETI Classic), as SETI BOINC is going through a fair amount of pain with an excessive and growing Waiting For Validation queue.
I know that I started shifting CPU cycles to Einstein from both my SETI classic and SETI BOINC systems starting back in June in response to the ongoing litany of issues that SETI BOINC has been enduring.
Over the past 30 days, Einstein has gotten something like 56% of my CPU cycles, with SETI seeing 29% and Climate getting 15%
A month ago, the split was 60% SETI and 40% Einstein, and for the month of June it was 71% SETI and 29% Einstein.
At some point I might change the resource shares to increase SETI back up, but at this point, quite frankly, that project, based on the past two to three months, will need to EARN a higher resource share by demonstrating a higher level of stability, reliabilty and overall performance.
RE: I'm starting to make a
)
I expected a whole new package but it seems that only a config file expands the existing package from 7 day wu's to 14 day wu's. Is there an explaination anywhere?
TIA and nice smooth transition too.
so his RAC should stay relatively the same.
That's the result I'm experiencing.
One of the effects for me is
)
One of the effects for me is that I am not running into 'overdues' as I was previously on some of my workstations -- especially those with shares with other projects in the mix. So for me, I 'stress' the systems here less as I no longer have to do 'resets'.
i'm happy about the new 14
)
i'm happy about the new 14 day deadline...because that synchs E@H up with now i can finally use the recommended BOINC 4.45 client...because now the client doesn't think i'm way behind on before...the einstein WU's always had the earliest deadline...so rarely was a seti unit crunched...now all is just fine.
RE: i'm happy about the new
)
Good point. It does make things less complicated.
If you’re saying you’ve been running 4.19 until now I think you will really like 4.45
After a couple of weeks running 4.45 you should be able to sit back and see BOINC almost always make all the right decisions based on your prefs.
I’m surprised that 4.45 didn’t work for you with the shorter deadline because for me it made running E@H way easier. After crunching continuous E@H wu’s no new E@H wu’s were downloaded until other projects caught up to their share. My problem was that the next round of E@H sometimes hit me with 1 wu more than I could process before deadline. Underestimated completion time was the root problem. Big concern that may already be solved.
RE: RE: i'm happy about
)
i'm already seeing 4.45 perform well...i was using Boinc 4.25 and had no problems before i upgraded...but 4.45 has more features...i think i'm gonna like it.