mersenneforum.org  

Go Back   mersenneforum.org > Great Internet Mersenne Prime Search > PrimeNet

Reply
 
Thread Tools
Old 2019-08-09, 00:17   #1
Chuck
 
Chuck's Avatar
 
May 2011
Orange Park, FL

7·112 Posts
Default Why does this user have so many repeated assignments?

I noticed this user in the list of exponents under 86M awaiting first-time checks. Why so many repeated assignments and expirations over a short period of time?

This is just one example. 85893593 The user has many others.
Chuck is online now   Reply With Quote
Old 2019-08-09, 04:56   #2
kriesel
 
kriesel's Avatar
 
"TF79LL86GIMPS96gpu17"
Mar 2017
US midwest

10000100000012 Posts
Default

Quote:
Originally Posted by Chuck View Post
I noticed this user in the list of exponents under 86M awaiting first-time checks. Why so many repeated assignments and expirations over a short period of time?

This is just one example. 85893593 The user has many others.
Hmm, this bears some looking into. It looks like he just checks them out and waits the 7 days to expiration with no progress of a Cat 0 assignment, and renews the reservations. He's had that exponent for 7 months and many reservations on that one. Re-reservation of an expired exponent that many times probably should not be allowed for Cat 0 exponents. I wonder if he has some script that returns them and then immediately reserves them before anyone else can be issued them.
Right now I count him holding 58 of the 374 exponents remaining to the 86M milestone, or 15.5%. And no progress indicated on any of them, despite months of opportunity. Even curtisc has only 34, 9.1%.
It would be a shame if it got to where we had to poach over 50 to make progress.

Last fiddled with by kriesel on 2019-08-09 at 05:17
kriesel is offline   Reply With Quote
Old 2019-08-09, 05:57   #3
axn
 
axn's Avatar
 
Jun 2003

10010001111002 Posts
Default

Could they be manually assigned exponents? Which means they are doing manual extensions and no direct communication (so no progress reports)? Has the user submitted any results recently?
axn is offline   Reply With Quote
Old 2019-08-09, 14:16   #4
Uncwilly
6809 > 6502
 
Uncwilly's Avatar
 
"""""""""""""""""""
Aug 2003
101×103 Posts

840610 Posts
Default

Quote:
Originally Posted by axn View Post
Could they be manually assigned exponents?
That was my thought.
Uncwilly is online now   Reply With Quote
Old 2019-08-09, 14:24   #5
chalsall
If I May
 
chalsall's Avatar
 
"Chris Halsall"
Sep 2002
Barbados

2×7×653 Posts
Default

Quote:
Originally Posted by Uncwilly View Post
That was my thought.
Nope. If you look at the associated assigned report you see an "Estimated Completion" value, which Manual Assignements don't show. Also, if you hover over the Userid value you see "Computer: n/a".

Lastly, this isn't a situation where the user is un-reserving and then re-reserving the assignment(s). In such cases, we wouldn't see the Expired entries.

Something very strange is going on...
chalsall is online now   Reply With Quote
Old 2019-08-09, 14:39   #6
kriesel
 
kriesel's Avatar
 
"TF79LL86GIMPS96gpu17"
Mar 2017
US midwest

10000100000012 Posts
Default

Quote:
Originally Posted by axn View Post
Could they be manually assigned exponents? Which means they are doing manual extensions and no direct communication (so no progress reports)? Has the user submitted any results recently?
patgie is no slouch in the LL first test area, at #17, 376 completed shown in https://www.mersenne.org/report_top_500_ll/ and moving up one spot in the past week, implying some recent completed work reported in.

I don't think these are normal manual assignments extended. First, there are 9 or ten expirations listed per exponent for the same username. Second, in my experience manual extension has no effect on actual assignment expiration.
Third, they have had since December to complete, but have not completed.
Fourth, most are now cat 0 assignments, and so according to https://www.mersenne.org/thresholds/ should not even be available for manual assignment. (But perhaps there is a record that when issued each was some higher cat level so they're "grandfathered in". Such an effect should go away when they expire.)

Case in point, of manual extension not working, if I look at my current assignment 332197331 nearing completion on a gpu, I can add 60 days to it via manual extension, raising it to over 1000 days as viewed at the manual extensions page https://www.mersenne.org/manual_extension/, but under My Account/Assignments https://www.mersenne.org/workload/ it still shows just 4 days left. The "updated" field says 2019-08-07 which is when I manually extended it to no effect on the https://www.mersenne.org/manual_extension/ expiration projection. I'm now attempting the 0.1% completion via primenet connected prime95 method of preventing an expiration of it. It's not looking promising:
Code:
[Comm thread Aug 9 09:23:05] Updating computer information on the server
[Comm thread Aug 9 09:23:06] Registering assignment: LL M332197331
[Comm thread Aug 9 09:23:07] PrimeNet error 40: No assignment
 [Comm thread Aug 9 09:23:07] ra: redundant LL effort, exponent: 332197331
(and also because the cpu on which its extension-by-slight-progress is being attempted would take days to run 0.1% of that exponent's LL test)

Again, please enable manual progress reporting for gpu manual CUDALucas runs and perhaps gpuowl v6.5.

Last fiddled with by kriesel on 2019-08-09 at 14:52
kriesel is offline   Reply With Quote
Old 2019-08-09, 15:15   #7
Uncwilly
6809 > 6502
 
Uncwilly's Avatar
 
"""""""""""""""""""
Aug 2003
101×103 Posts

2×32×467 Posts
Default

Quote:
Originally Posted by chalsall View Post
Lastly, this isn't a situation where the user is un-reserving and then re-reserving the assignment(s). In such cases, we wouldn't see the Expired entries.

Something very strange is going on...
Maybe a manually created worktodo entry that for some reason is getting restored? Like the machine is going back to a restore point.

§The entry is in there and there hasn't yet been a coms with with the server.
There is coms, it gets assigned.
Then at some point we Ground Hog Day back to §

Last fiddled with by Uncwilly on 2019-08-09 at 15:16
Uncwilly is online now   Reply With Quote
Old 2019-08-09, 17:43   #8
kriesel
 
kriesel's Avatar
 
"TF79LL86GIMPS96gpu17"
Mar 2017
US midwest

52·132 Posts
Default

Quote:
Originally Posted by chalsall View Post
Something very strange is going on...
Indeed. All 58 say Computer: n/a. Maybe this is a behavior of a client management program for gpu LL runs (llloop, mersenne manager)? There are very few values of days to expiration among these 58.
Many say 3; several say 9; three say 79, two say 4 days.
There are only 3 assigned dates: 2019-07-29, 2019-08-05, 2019-08-06.

Last fiddled with by kriesel on 2019-08-09 at 17:46
kriesel is offline   Reply With Quote
Old 2019-08-10, 00:07   #9
Madpoo
Serpentine Vermin Jar
 
Madpoo's Avatar
 
Jul 2014

1100110010012 Posts
Default

I'll have to look into it and see what's what.

My first guess is that the machine is stalled but still reporting in periodically? The exponent expires but because this machine still checks in, and maybe has 0.01% done (so there's a minute amount of progress), it checks in and the server obligingly hands out a fresh assignment for it.

Eventually that won't work anymore because it's in the cat 0 range and someone else is going to get the assignment between when it next expires and when that computer finally contacts the server.

Looking at some logs may help confirm or refute that theory.
Madpoo is offline   Reply With Quote
Old 2019-08-10, 13:49   #10
petrw1
1976 Toyota Corona years forever!
 
petrw1's Avatar
 
"Wayne"
Nov 2006
Saskatchewan, Canada

3·5·172 Posts
Default

Assignments consistently expired after 20 days and reassign a day later.
petrw1 is offline   Reply With Quote
Old 2019-08-10, 15:44   #11
kriesel
 
kriesel's Avatar
 
"TF79LL86GIMPS96gpu17"
Mar 2017
US midwest

52×132 Posts
Default

Taking 85532177 as an example, reissue to the same user after no discernible progress can be seen to occur at 31 days, 21 days, and 8 days, progressively. So he's apparently having no trouble getting them back again the day after they've expired.
That's of order 500 to 600 reassignments after expiration. (58 exponents x ~10 reassigns each average).

There is a counterexample where he did not get one back after expiration. It's rare; I found one such, see below.

Cat 2: "Assignments are recycled if assignment is not started within 30 (unless manual testing) days or when the exponent moves midway into the first category and the assignment is more than 180 days old."
Cat 1: "Assignments are recycled if assignment is not started within 20 days or does not report in for 30 days or when assignment is more than 90 days old."
Cat 0: "Assignments are recycled if assignment is not started with 7 days or when assignment is more than 30 days old."
https://www.mersenne.org/thresholds/

He's holding at 58 reserved immobile exponents below 86M first time test. Some 29 expire in 2 days. We'll see how many of these he has assigned again in 3-4 days.

Is it possible to designate a user as needing to do double checks?
Each of these stuck exponents soon to hold up the first-time milestone could be done start to finish in less than 4 days on a decent gpu. So one decent gpu could have done them all by now. He's had them for about 8 months and there's no progress indicated on any of them.

It does appear patgie eventually finishes some with such a history. Checking 85532000 to 85600000,
http://www.mersenne.ca/exponent/85534817 patgie completed
http://www.mersenne.ca/exponent/85574777 patgie completed
http://www.mersenne.ca/exponent/85580321 patgie completed
http://www.mersenne.ca/exponent/85580993 patgie completed
http://www.mersenne.ca/exponent/85583417 patgie completed

http://www.mersenne.ca/exponent/85538993 someone else got and completed after it was assigned to patgie and expired. It's much more common that he acquires an assignment that expired on someone else and then is repeatedly able to get it assigned to him.

I suspect patgie is running a reassignment script timed closely after the server runs its checks for expiration and makes them available for assignment. Not bulletproof, but would have high odds of success if the time offset is short compared to the server's expiration check interval (24 hours?)
Compare patgie's assignments on August 13 to the following:

Code:
As of Aug 9:
exponent   work stage% days  ETA     Assigned    Last update   Next Update   Est. Complete  UserID
           type        left
85532177    LL           3    15    2019-08-05    2019-08-05    2019-08-06    2019-08-24    patgie
85533977    LL           3    17    2019-08-05    2019-08-05    2019-08-06    2019-08-26    patgie
85550033    LL           3     7    2019-08-05    2019-08-05    2019-08-06    2019-08-16    patgie
85570697    LL           3    38    2019-08-05    2019-08-05    2019-08-06    2019-09-16    patgie
85575233    LL           3     6    2019-08-05    2019-08-05    2019-08-06    2019-08-15    patgie
85583297    LL           3    15    2019-08-05    2019-08-05    2019-08-06    2019-08-24    patgie
85585673    LL           3    34    2019-08-05    2019-08-05    2019-08-06    2019-09-12    patgie
85589681    LL           3     6    2019-08-05    2019-08-05    2019-08-06    2019-08-15    patgie
85607897    LL           3    15    2019-08-05    2019-08-05    2019-08-06    2019-08-24    patgie
85622177    LL           3    24    2019-08-05    2019-08-05    2019-08-06    2019-09-02    patgie
85628513    LL           3     7    2019-08-05    2019-08-05    2019-08-06    2019-08-16    patgie
85629737    LL           3    34    2019-08-05    2019-08-05    2019-08-06    2019-09-12    patgie
85669601    LL           3     6    2019-08-05    2019-08-05    2019-08-06    2019-08-15    patgie
85670393    LL           3     7    2019-08-05    2019-08-05    2019-08-06    2019-08-16    patgie
85673201    LL           3    15    2019-08-05    2019-08-05    2019-08-06    2019-08-24    patgie
85674521    LL           3    24    2019-08-05    2019-08-05    2019-08-06    2019-09-02    patgie
85674881    LL           3    34    2019-08-05    2019-08-05    2019-08-06    2019-09-12    patgie
85677377    LL           3     6    2019-08-05    2019-08-05    2019-08-06    2019-08-15    patgie
85684721    LL           3    15    2019-08-05    2019-08-05    2019-08-06    2019-08-24    patgie
85686521    LL           3    24    2019-08-05    2019-08-05    2019-08-06    2019-09-02    patgie
85687817    LL           3    34    2019-08-05    2019-08-05    2019-08-06    2019-09-12    patgie
85692521    LL           4     3    2019-08-06    2019-08-06    2019-08-07    2019-08-12    patgie
85697321    LL           3     6    2019-08-05    2019-08-05    2019-08-06    2019-08-15    patgie
85699433    LL           3    15    2019-08-05    2019-08-05    2019-08-06    2019-08-24    patgie
85708793    LL           3    24    2019-08-05    2019-08-05    2019-08-06    2019-09-02    patgie
85722473    LL           3    34    2019-08-05    2019-08-05    2019-08-06    2019-09-12    patgie
85728641    LL           3     6    2019-08-05    2019-08-05    2019-08-06    2019-08-15    patgie
85732553    LL           3    15    2019-08-05    2019-08-05    2019-08-06    2019-08-24    patgie
85732601    LL           3    24    2019-08-05    2019-08-05    2019-08-06    2019-09-02    patgie
85733201    LL           4     3    2019-08-06    2019-08-06    2019-08-07    2019-08-12    patgie
85742897    LL           3    34    2019-08-05    2019-08-05    2019-08-06    2019-09-12    patgie
85745921    LL           3     6    2019-08-05    2019-08-05    2019-08-06    2019-08-15    patgie
85749953    LL           9     4    2019-07-29    2019-07-29    2019-07-30    2019-08-13    patgie
85750337    LL           9     8    2019-07-29    2019-07-29    2019-07-30    2019-08-17    patgie
85752977    LL           9    12    2019-07-29    2019-07-29    2019-07-30    2019-08-21    patgie
85753001    LL           9    16    2019-07-29    2019-07-29    2019-07-30    2019-08-25    patgie
85761833    LL           9    20    2019-07-29    2019-07-29    2019-07-30    2019-08-29    patgie
85765793    LL    LL    79    -7    2019-07-29    2019-07-29    2019-07-30    2019-08-02    patgie
85790153    LL           9     5    2019-07-29    2019-07-29    2019-07-30    2019-08-14    patgie
85797617    LL           9     9    2019-07-29    2019-07-29    2019-07-30    2019-08-18    patgie
85808081    LL           9    13    2019-07-29    2019-07-29    2019-07-30    2019-08-22    patgie
85810601    LL           9    17    2019-07-29    2019-07-29    2019-07-30    2019-08-26    patgie
85826057    LL           9    21    2019-07-29    2019-07-29    2019-07-30    2019-08-30    patgie
85842857    LL    LL    79    -7    2019-07-29    2019-07-29    2019-07-30    2019-08-02    patgie
85845377    LL           9    -3    2019-07-29    2019-07-29    2019-07-30    2019-08-06    patgie
85855361    LL           9     1    2019-07-29    2019-07-29    2019-07-30    2019-08-10    patgie
85893377    LL           9     5    2019-07-29    2019-07-29    2019-07-30    2019-08-14    patgie
85893593    LL           9     9    2019-07-29    2019-07-29    2019-07-30    2019-08-18    patgie
85898873    LL           9    13    2019-07-29    2019-07-29    2019-07-30    2019-08-22    patgie
85910177    LL           9    17    2019-07-29    2019-07-29    2019-07-30    2019-08-26    patgie
85910897    LL           9    21    2019-07-29    2019-07-29    2019-07-30    2019-08-30    patgie
85919081    LL    LL    79    -7    2019-07-29    2019-07-29    2019-07-30    2019-08-02    patgie
85938521    LL           9     5    2019-07-29    2019-07-29    2019-07-30    2019-08-14    patgie
85943201    LL           9     9    2019-07-29    2019-07-29    2019-07-30    2019-08-18    patgie
85967393    LL           9    -7    2019-07-29    2019-07-29    2019-07-30    2019-08-02    patgie
85970561    LL           9    -3    2019-07-29    2019-07-29    2019-07-30    2019-08-06    patgie
85972097    LL           9     1    2019-07-29    2019-07-29    2019-07-30    2019-08-10    patgie
85976993    LL           9     1    2019-07-29    2019-07-29    2019-07-30    2019-08-10    patgie

Last fiddled with by kriesel on 2019-08-10 at 16:10
kriesel is offline   Reply With Quote
Reply

Thread Tools


Similar Threads
Thread Thread Starter Forum Replies Last Post
Add repeated digits after a number until it is prime sweety439 sweety439 73 2019-08-02 10:18
Completed assignments still in GPU72 Assignments page kladner GPU to 72 3 2019-06-15 01:19
Assignments Completed by Another User linament PrimeNet 99 2015-08-26 21:40
x86 Microcode Execution Unit and repeated-address implied loads ewmayer Hardware 8 2014-10-07 08:17
Trivial bug: repeated PM notifications Christenson Forum Feedback 0 2011-03-21 03:49

All times are UTC. The time now is 21:20.

Sun Aug 9 21:20:56 UTC 2020 up 23 days, 17:07, 3 users, load averages: 1.68, 1.70, 1.88

Powered by vBulletin® Version 3.8.11
Copyright ©2000 - 2020, Jelsoft Enterprises Ltd.

This forum has received and complied with 0 (zero) government requests for information.

Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 or any later version published by the Free Software Foundation.
A copy of the license is included in the FAQ.