PrimeGrid
Please visit donation page to help the project cover running costs for this month

Toggle Menu

Join PrimeGrid

Returning Participants

Community

Leader Boards

Results

Other

drummers-lowrise
1) Message boards : Seventeen or Bust : Proposal: A new Sierpiński problem (Message 140572)
Posted 2 hours ago by Profile Michael GoetzProject donor
Almost all pending tests has been returned, but 53 are still in progress.


7 of those are mine. They'll be completed in a few hours.
2) Message boards : Number crunching : many PPSsieve units are pending? (Message 140571)
Posted 2 hours ago by Profile Michael GoetzProject donor
In case you weren't aware, the number of pending tasks is entirely dependent upon what other users are doing. High or low pending numbers have nothing to do with what's happening on the server.


Yes, but 25 just today (UTC) waiting for validation (35 total) is much higher than normal. So, how is the server?


You're waiting for your wingmen to return their tasks.

Likely reason for having a wingman problem right now:

There's a user who, possibly because of incorrect settings on BOINCStats BAM!, has about 60 thousand in-progress PPS Sieve tasks. To put this in perspective, there's normally about 20 to 30 thousand in progress PPS Sieve tasks TOTAL across the entire system. He's got three times as many tasks as everyone else combined. You (and everyone else) is waiting either for this guy's computers to complete the tasks, or for them to time out and and be sent to someone else.

Nothing is wrong, but you will need to wait a bit longer for these tasks to be validated.
3) Message boards : Number crunching : many PPSsieve units are pending? (Message 140558)
Posted 7 hours ago by Profile Michael GoetzProject donor
In case you weren't aware, the number of pending tasks is entirely dependent upon what other users are doing. High or low pending numbers have nothing to do with what's happening on the server.
4) Message boards : General discussion : Please dont "Shut up" :) (Message 140549)
Posted 11 hours ago by Profile Michael GoetzProject donor
When you say a ways to go, do you have any rough estimates on how long taking into consideration how many GFN-17 low are completed on average....also could we speed it up with a concentrated effort from a lot of us and would this get us moving onto new things faster or would it still be a very long way off? I like the thoughts Michael put forward actually and it sounds quite interesting


Finishing GFN-17 (or, really, any other project) has nothing to do with the work necessary to start other projects, so no, that won't get you moving any faster on new stuff.

GFN-17 was started almost exactly 5 years ago.

It will end at b=42,597,774.

We're currently at b=19,967,566, or 47%.

Based on that, you could say we have about 5 years to go, except that computers keep getting faster. My guess would therefore be somewhere around 2 to 3 years.

17-Low isn't as popular as 17-MEGA, for obvious reasons. The MEGA version has done about 50% more than the LOW version.
5) Message boards : Number crunching : Strange Behaviour (Message 140509)
Posted 3 days ago by Profile Michael GoetzProject donor
I think someone (possibly Mike) somewhere(possibly on this forum) addressed this problem before too, but why does the BOINC Client/Manager abort tasks according to their initial deadline instead of PG's or Stream's server's extended deadline? About 30 of Jeppe's problem's tasks were aborted, and at 7:26PM (11:26AM UTC, 1hr8min later) another around 20 GFN14 DC tasks will be aborted. Can there be any changes made to this?

Because these tasks were unstarted. Nothing will be lost aborting them, so both client and server a free to re-issue them.

Deadline extension works only work for in-progress tasks (they will send a special keep-alive message to server).


Really? That's strange. On my task page on your server it says "1st Jun 9:42:55 UTC" for those aborted LLR2 tasks, but on the BOINC Manager they say 30th May 5:42:55PM local time, which is 30th May 9:42:55 UTC. How does that happen?


The tasks have a 7-day deadline -- that's May 30th, and that's the ONLY date your computer knows.

On the server side, there's a global "grace period" setting which stream apparently also set to 7 days. The grace period is the amount of time, *after* the deadline, that the server waits before sending out a replacement task. The purpose is to prevent the server from needlessly sending out duplicate tasks in case the host computer is just a little bit late. (FYI, the PrimeGrid server is set to have a 25 hour grace period.)

What happened is that your tasks passed the deadline on May 30th (7 days), and the BOINC client did what it's supposed to do and aborted any expired tasks that had not yet been started. The date you see on the website isn't really the deadline; it's the date at which the server will send out a replacement task. It's intentionally later than the deadline.
6) Message boards : Number crunching : Strange Behaviour (Message 140503)
Posted 3 days ago by Profile Michael GoetzProject donor
I think someone (possibly Mike) somewhere(possibly on this forum) addressed this problem before too, but why does the BOINC Client/Manager abort tasks according to their initial deadline instead of PG's or Stream's server's extended deadline? About 30 of Jeppe's problem's tasks were aborted, and at 7:26PM (11:26AM UTC, 1hr8min later) another around 20 GFN14 DC tasks will be aborted. Can there be any changes made to this?


Any tasks that have not been started will be automatically aborted by the BOINC client on your computer when they exceed the deadline. The client has no knowledge of the deadline on the server. It only knows about the original deadline it was sent when it received the task.
7) Message boards : Seventeen or Bust : Proposal: A new Sierpiński problem (Message 140449)
Posted 8 days ago by Profile Michael GoetzProject donor
Also, it seems you can still get new tasks. You just can't upload the results to the server.
8) Message boards : Seventeen or Bust : Proposal: A new Sierpiński problem (Message 140448)
Posted 8 days ago by Profile Michael GoetzProject donor
The FUH on the server is reporting that it's out of disk space.


Is this something that will not be fixed until tomorrow due to timezone? I am trying to figure out if I should just wait, or fire up some other project until this is fixed.


Timezones work to our advantage in this case, as the sun will be coming on on stream in an hour or two.
9) Message boards : Seventeen or Bust : Proposal: A new Sierpiński problem (Message 140445)
Posted 8 days ago by Profile Michael GoetzProject donor
The FUH on the server is reporting that it's out of disk space.
10) Message boards : Seventeen or Bust : The SOB Double Check will end... aka The Way Too Early Prediction Thread (Message 140437)
Posted 9 days ago by Profile Michael GoetzProject donor
It will be interesting to see which happens first: we finish the DC or Elon Musk successfully lands something on Mars. Not a person, but any sort of lander.

As for predictions, I think you're in the right ballpark.


Was looking through old posts, and of course we finished it earlier than Elon Musk :P

Also,
Understand that both Jim and myself are really paranoid about business continuity, and it's hard to imagine any sort of disaster that would result in the data being lost. I can think of things that would shut PrimeGrid down permanently, but the data would survive such an event. I might need to use sneakernet to distribute the data (the proverbial station wagon filled with 9-track tapes), but short of a nuclear holocaust hitting multiple locations, the data is well preserved. And if there's s single event that takes out both the data center and the secondary storage site, which is hundreds of miles away, I suspect what's left of civilization won't be worrying about our data.

What would shut down PG permanently? Just asking.


Rytis dies of Covid-19? Everyone gets bored and stops crunching? All the admins get tired and nobody else wants to do it? World War III? Economic disruption from the pandemic is so bad that we can't afford to keep the project running?

The USUAL things that kill a project are either "disk crashed and I lost all the data", or "server died and I can't afford to replace it." Those are not things most hobbyists plan for (or even most University-run projects). PrimeGrid's pretty well protected against that kind of failure.


Next 10 posts
[Return to PrimeGrid main page]
DNS Powered by DNSEXIT.COM
Copyright © 2005 - 2020 Rytis Slatkevičius (contact) and PrimeGrid community. Server load 0.93, 1.30, 1.56
Generated 3 Jun 2020 | 0:52:39 UTC