Date: Tue, 25 Aug 2015 23:16:58 -0400 From: <jfoug@....net> To: john-users@...ts.openwall.com Subject: Re: The ETA for -single is somewhat useless ---- Solar Designer <solar@...nwall.com> wrote: > On Tue, Aug 25, 2015 at 01:30:58PM -0500, JimF wrote: > > At least for slower hashes, with a large working set and or few rules. > > The ETA simply does not show up, and when it does, it is at 50% or 75%, > > etc and stays there for a LONG time. I am not sure how easy getting this > > working properly would be, but as it stands, it has no useful value. > > > > This is not a bug we can simply fix in jumbo. It is a john-proper issue. > > This problem is only that bad when you have unusually few rules. With > the default ruleset, the reported percentage of work done usually grows > in 1% steps. > > Also, it's not just a reporting issue: this granularity coincides with > how much work will be redone if you interrupt and restore. If this is a buffered granularity issue (which became VERY apparent with the number of candidates in formats like sha512crypt in recent CMIYC). and we pre-build this buffer, and track it while running, then we could write code to store off this list, and upon resume reload it. In the same manner, ETA could be deal with at time of actual work being done, vs jumping to 50%, and sitting there for a day, then jumping to DONE and sitting there for a day. Like I mentioned in the github issue posted about this issue, there is almost no usefulness for ETA for this situation. Yes, it does give you a bit of insite to the amount of queue'd work, but any form of ETA is pretty laughable. I am told the run will be over in a couple minutes (when it starts out), and then 20 hours later it is over. I did not say it was an easy problem, just that if it 'can' be improved upon, then possibly we should look into it.
Powered by blists - more mailing lists
Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.