Posts by Nick

1) Message boards : Number crunching : large swing in ETA (Message 2555)
Posted 8 Sep 2019 by Nick
Post:
I already had a suspicion that there's a problem with the deadline here. Thanks for pointing out that _1 means that it's a retry, I hadn't known that. On my 32-core machine, I have 11 _1 WUs running right now, so 1/3rd of the work I'm doing is retry work. That seems high to me.

What's the deadline, is it the deadline for starting the task? Finishing the task? The task being sent out to another user? If the deadline passes and I'm almost done (I have seen this countless times on this sf4-16x271), will I continue to compute it unless the retry beats me to it or does it get cancelled either some fixed time later or on the next sync with the server?


The deadline is 1 week and then there is a 3 day grace period before it is reissued (or maybe the grace period only applies to receiving credit?). The client is usually pretty good at aborting tasks that haven't started before the deadline. If you're contacting the server regularly (once per day or more) I don't think you have anything to worry about.

The "reduced delay bound" is set to .5 which means reissued tasks have 3.5 days to complete. I would assume the 3 day grace period still applies on accelerated retries, so in effect you would have 6.5 days on retries.

Hope that explains things.


Thanks for the explanation!

I note that the ETA has swung back the other way and is now back at 24 days. I haven't documented it, but I have noticed that this swing happens every week and expect it will go back up by next Friday night and back down again as the weekend draws to a close.
2) Message boards : Number crunching : large swing in ETA (Message 2551)
Posted 6 Sep 2019 by Nick
Post:
I already had a suspicion that there's a problem with the deadline here. Thanks for pointing out that _1 means that it's a retry, I hadn't known that. On my 32-core machine, I have 11 _1 WUs running right now, so 1/3rd of the work I'm doing is retry work. That seems high to me.

What's the deadline, is it the deadline for starting the task? Finishing the task? The task being sent out to another user? If the deadline passes and I'm almost done (I have seen this countless times on this sf4-16x271), will I continue to compute it unless the retry beats me to it or does it get cancelled either some fixed time later or on the next sync with the server?
3) Message boards : Number crunching : large swing in ETA (Message 2548)
Posted 6 Sep 2019 by Nick
Post:
Since yesterday, the estimated completion time grew by 10 days. I'm wondering if this might indicate a problem with the settings on the project. Is there a large number of WUs whose deadline expired?
4) Message boards : News : GPU app status update (Message 2403)
Posted 16 Apr 2019 by Nick
Post:
It might be worth reporting back your findings to the PARI people, and suggesting that they compare notes with FFTW to see if similar techniques could be employed.


Somebody else suggested this too. I do plan on contacting them. The issue might be that they picked an algorithm that worked well in general for any degree; mine is specialized to degree 10.


How did you specialize it?

Do you think the technique could be generalized so that more efficient specialized algorithms could be produced for any fixed degree?
5) Message boards : Number crunching : sf6 WUs 7x8 and 9x7 missing from batch status (Message 2158)
Posted 24 Feb 2019 by Nick
Post:
I've got work units "wu_sf6_DS-7x8_Grp11032of20480_0" (and others) as well as "wu_sf6_DS-9x7_Grp5785of6144_0", but on the batch status page for Search 6 M=7 starts with N=9 and up, no N=8 and M=9 starts at N=9, no N=7 (or N=8). Is the batch status page just missing some rows?

Also, how do we decide which WUs to work on next? Why not sf5 DS14x11?





Main page · Your account · Message boards


Copyright © 2019 Arizona State University