There are even stats updates again.It would appear that ODLK server is catching up!
The second 18 hours:
There are even stats updates again.It would appear that ODLK server is catching up!
I must have looked at wrong tables. Credits per task and credits per time are actually very similar between ODLK1 and ОДЛК. We should pass Gridcoin and Taiwan in the ОДЛК marathon this weekend.Hmm. We received 2.4 M points during the ODLK1 sprint. However, while ODLK1 and ОДЛК have similar task run times, the latter has only ~1/10 of the credits per task. That way we won't make it further up in the marathon during the next 3 days.
.... Hopefully ... the Stats will update properly before the end of the Sprint.
Ah, so that's why the "Sprint Killed ODLK's Website".Pretty sure it was the two C2D laptops I added when I joined.
Getting close to catching SUSA. Hopefully when/if it does happen the Stats will update properly before the end of the Sprint.
Looking at my pending/stalled uploads and downloads, I am seeing many more downloads than uploads in progress or stuck. And this makes sense given that the ODLK server is at the admin's home, certainly behind an asymmetric connection with distinctly lower upload bandwidth than download bandwidth (from the server's POV, IOW lower download bandwidth than upload bandwidth from our POV).Hmmm, I wonder what happens if they don't? I would hope Sebastian would manually update like crazy for a few minutes before accepting hours old data, but I don't assume that.
And I am running out of work as all my uploads AND downloads are not happening.
Until a few hours ago, I got only many HTTP timeouts and some successful transactions. Now I get this:
"Scheduler request failed: Server returned nothing"
But there are some successful requests still, like so:
"Reporting 20 completed tasks
Not requesting tasks: too many uploads in progress
Scheduler request completed"
This is not Sunday morning the project admin was hoped for.Until a few hours ago, I got only many HTTP timeouts and some successful transactions. Now I get this:
"Scheduler request failed: Server returned nothing"