Page 2 of 2
Re: 171.64.65.54 overloaded / NOT accepting
Posted: Tue Jun 15, 2010 4:15 pm
by noorman
.
Anyway, at the moment there are more SMP servers than before, although I 'm not sure they all are 'in the loop' yet !?
.
Re: 171.64.65.54 overloaded / NOT accepting
Posted: Tue Jun 15, 2010 4:21 pm
by Zagen30
noorman wrote:lanbrown wrote:Grandpa_01 wrote:Just remember it is not just you loosing we all are. The server does not care who you are or who I am so we all get to loose equally.
Not true at all. Let's say it takes 26 hours to complete a WU and the server is down for 24-hours.
Contributor A get a WU 25 hours before the server goes down. So that means an hour before the WU is completed, the server goes down and will be down for a day.
Contributor B has a system with equivalent performance and gets a new WU an hour before the server goes down. The server will be back on-line before the WU is completed.
Contributor A loses bonus points, contributor B does not.
.
It 's indeed all about timing !
The same goes for Stats; Stanford now has a 2 hour refresh rate (I believe) and f.e. EOC Stats stiil has the 3 hour cycle, which also skews data and points !
.
But that just accounts for when the credit shows up, not how much credit you receive. I'm pretty sure the bonus is calculated based on when the server first gets the WU back, not when the stats totals are updated. EOC has absolutely nothing to do with how many points you actually get- it just reads off your point totals every 3 hours and calculates how many you earned since the previous update. While EOC is often a bit later to show your points, they will all show up at some point.
Re: 171.64.65.54 overloaded / NOT accepting
Posted: Tue Jun 15, 2010 4:29 pm
by kasson
Yes, we have increased the number of SMP servers. If you're having trouble getting work, try running with the -advancedmethods option; one server is just on advanced methods at the moment (and has plenty of work available). We apologize for the extended downtime on server .54; we'll post additional status information when we have it available.
Re: 171.64.65.54 overloaded / NOT accepting
Posted: Tue Jun 15, 2010 4:44 pm
by noorman
.
thanks for that, Dr. Kasson
.
Re: 171.64.65.54 overloaded / NOT accepting
Posted: Tue Jun 15, 2010 4:53 pm
by noorman
noorman wrote:lanbrown wrote:Grandpa_01 wrote:Just remember it is not just you loosing we all are. The server does not care who you are or who I am so we all get to loose equally.
It 's indeed all about timing !
The same goes for Stats; Stanford now has a 2 hour refresh rate (I believe) and f.e. EOC Stats still has the 3 hour cycle, which also skews data and points !
.
But that just accounts for when the credit shows up, not how much credit you receive. I'm pretty sure the bonus is calculated based on when the server first gets the WU back, not when the stats totals are updated. EOC has absolutely nothing to do with how many points you actually get- it just reads off your point totals every 3 hours and calculates how many you earned since the previous update. While EOC is often a bit later to show your points, they will all show up at some point.
.
I know that EOC Stats (or any stats for that matter) don't have anything to do with how much you are credited for any WU, but it 's the timing of points coming in that make for a higher or lower average in your count !
If you 've finished a WU that can't be uploaded for 24 hrs (f.e.), that makes no difference in the total points count, but it surely does count when you put those figures in to an averaging algorithm ...
Another point is the control; if every credit comes in in time, you can easily track that, but if things get shifted in time, it can get very difficult to check indeed !
.
Re: 171.64.65.54 overloaded / NOT accepting
Posted: Tue Jun 15, 2010 7:39 pm
by kasson
The system is back up for the moment; we're still having issues with the second RAID, so it will need to go down at some point in the future. We've reminded our sysadmins how important it is for donors to have this system up, and we'll try to keep it in production for as much of this work period as possible.
Re: 171.64.65.54 overloaded / NOT accepting
Posted: Tue Jun 15, 2010 8:00 pm
by AlanH
BUMP. Reported earlier in this thread.
AlanH wrote:My system returned a unit to this server yesterday but it is not shown as credited.
Code: Select all
[19:05:46] Folding@home Core Shutdown: FINISHED_UNIT
[19:05:47] CoreStatus = 64 (100)
[19:05:47] Unit 6 finished with 90 percent of time to deadline remaining.
[19:05:47] Updated performance fraction: 0.877645
[19:05:47] Sending work to server
[19:05:47] Project: 6060 (Run 0, Clone 4, Gen 80)
[19:05:47] + Attempting to send results [June 14 19:05:47 UTC]
[19:05:47] - Reading file work/wuresults_06.dat from core
[19:05:47] (Read 3801645 bytes from disk)
[19:05:47] Connecting to http://171.64.65.54:8080/
[19:07:08] Posted data.
[19:07:09] Initial: 0000; - Uploaded at ~45 kB/s
[19:07:09] - Averaged speed for that direction ~22 kB/s
[19:07:09] + Results successfully sent
[19:07:09] Thank you for your contribution to Folding@Home.
[19:07:09] + Number of Units Completed: 87
This may be a different problem from the others reported for this server. My case was not a failure to accept the unit - it was uploaded, but has never been credited. Any chance this credit will ever appear? My system is now crawling through a two-day 6701 marathon that will probably result in very low points. The combination of a non-credited submission plus a 6701 will stick a major crimp in my PPD this week.
I'm user ID AlanH on Team 47958.
Re: 171.64.65.54 overloaded / NOT accepting
Posted: Tue Jun 15, 2010 8:11 pm
by noorman
.
It has happened before that credits were not forthcoming as quickly as usual, but almost never is data lost.
It may be on the broken system, but in time this will be recovered, as will the credits for that WU.
I can't check this, but I think one of the Mods can.
I 'm just telling you what has happened during past system failures where people were waiting for their credits
There 's enough data in your post to look it up ...
.
Re: 171.64.65.54 overloaded / NOT accepting
Posted: Tue Jun 15, 2010 9:54 pm
by AlanH
Thanks for the reassurance. My concern was that I hadn't seen anyone else report a complete lack of credit for a submitted unit, so I was concerned that the unit might have been lost forever. However, interestingly, it has just been credited in EOC's stats, so I guess I posted my bump too soon.
Re: 171.64.65.54 overloaded / NOT accepting
Posted: Tue Jun 15, 2010 10:00 pm
by noorman
AlanH wrote:Thanks for the reassurance. My concern was that I hadn't seen anyone else report a complete lack of credit for a submitted unit, so I was concerned that the unit might have been lost forever. However, interestingly, it has just been credited in EOC's stats, so I guess I posted my bump too soon.
.
Well, you nor I could have known when it would come; I just was 99% sure that it would come at some time.
As I said, I think it got caught up in the .54 crash ...
.
Re: 171.64.65.54 overloaded / NOT accepting
Posted: Wed Jun 16, 2010 7:49 am
by bruce
Hi AlanH (team 47958),
Your WU (P6060 R0 C4 G80) was added to the stats database on 2010-06-15 12:06:27 for 2188.55 points of credit.
Re: 171.64.65.54 overloaded / NOT accepting
Posted: Wed Jun 16, 2010 5:46 pm
by AlanH
Thanks Bruce. I have already commented that it arrived, which is good news for the science as well as my points