Good day.

http://www.enigmaathome.net/server_status.php

Available workunits:
m3_pldrv59_2
# of workunits: 540000
done 548518
remaining 0
in progress 325

can you please add one more line to every WU pool - time to complete?

we know: Workunits validated last hour 203

so TTC = in progess / WU's validated = time in hours.

---

======
wbr, Me. Dead J. Dona

It won't work like that, mostly because the server doesn't know the actual processing rate. It jumps up and down when various daemons are started or stopped (the server automatically disables validators when the load gets too high); also it's totally impossible to predict *when* the workunit will come back from the client. Most of the workunits are back really fast (average turnaround time is less than 2 days), however the rest may come back close to deadline or never at all, so the processing rate slows down while the age of workunit batch increases. It's always slowest near the end, when the server has to wait for resends.

---

M4 Project homepage
M4 Project wiki

well that's why it's called ESTIMATE ))

i suppose it's better to have some even inaccurate rates, rather than nothing.


pleeease

---

======
wbr, Me. Dead J. Dona

Then what kind of estimate would you like ?

The search for message key is based purely on luck multiplied by the strenght of the algorithm and dictionaries used.
Every single workunit has equal chance to break the message, so I can't predict when (or IF) it will be broken. Reaching end of the batch means that it failed and it's a thing I'd like to avoid.

---

M4 Project homepage
M4 Project wiki

Hi,

Well, more statistics will not help us to solve the message, (faster or better algorithm will...) however, since we already have some stats on the server...

Lets suppose that algorithm is good and WILL find the solution. If we are really not lucky, the solution can happen to be THE LAST combination tried....

With this supposition in mind, "Death [Kiev]" would probably like to see what percentage of the whole job is making each work-unit batch, what percentage of the batch has been already returned (yes, everybody can calculate it from existing stats) and VERY ROUGH time estimate of the time needed to complete the batch based on AVERAGE return rate for the batch (for instance last 48 hours - or week average or something like this).... just to have a better idea where we are standing...

Given the above mentioned the daily rate of processing the new batch m4_vroln72_4 is now about 89000 work units in average.

With that speed the remaining batch of m4_vroln72_4 will terminate in about
500 days if no solution is found earlier.

As some have said before,nobody can estimate when the break eventually will come.

Anyway,I think this whole operation is very exciting indeed to participate in over more years to come.

And patience over time is needed trying to fulfill our goals here.
So did the real codebreakers also do in BP during WW2 !