Hello Roch:

Rochester wrote:Predict day count every time go low by more 1 week, but that is wronged. I say you ready November. You can report every month now, no need every week.

The number of results/week is not constnt and is often increasing, hence the remaining time is lowering a bit faster.

Here is an example: imagine that you are downloading a file of 100 MB. The first minute of the download was at a low speed and it only downloaded 100 KB/sec in average. I would calculate the expected remaining time in the following way:

Code: Select all

```
1 minute ---> 100 KB/s ~ 5.86 MB
Expected total time ---> 100 MB
Expected total time ~ (100/5.86)*(1 minute) ~ 17 min. 4 sec.
Expected remaining time = Expected total time - spent time = 17'04" - 1' = 16'04"
```

Now, the download speed increases and it averages 200 KB/s in the next two minutes. Then:

Code: Select all

```
Downloaded: (100 KB/s)*(1 minute) + (200 KB/s)*(2 minutes) ~ 5.86 MB + 23.44 MB ~ 29.3 MB
Expected total time ~ (100/29.3)*(1 minute + 2 minutes) ~ 10 min. 14 sec.
Expected remaining time = Expected total time - spent time = 10'14" - 3' = 7'14".
```

The expected remaining time lowered by more than two minutes.

The total number of results (96,400,068) play the role of 100 MB of the example. A drawback is that 1 MB is equal to other MB but each result has different number of nodes, but I will assume that in the long term, the larger ones compensate with the smaller ones, resulting in more less average results.

I estimate the remaining time in this way:

Code: Select all

```
Expected total time = [96,400,068/(total number of results calculated)]*(elapsed time in these calculations)
Expected remaining time = Expected total time - elapsed time = [96,400,068/(total number of results calculated) - 1]*(elapsed time)
```

In the case of this week:

Code: Select all

`Expected remaining time ~ (96.4M/36.7M - 1)*(578 days) ~ 940 days ~ 134 weeks + 2 days from now (02-Oct-2018).`

Which is the same than Steven predicted in his last post. There were circa 29.5 million results on 03-Jan-2016; there are circa 36.7 million results on 06-Mar-2016, that is, in a period of time of nine weeks = 63 days. The average speed in this period is more less (36.7M - 29.5M)/63 ~ 114.3k results/day. If Steven manages to keep this speed, then there are still 96.4M - 36.7M = 59.7M results and the expected remaining time at that speed (which is way higher than 57.3k results/day, because this speed includes time when the calculations were much slower than nowadays) is (59.7M results)/(114.3k results/day) ~ 522 days = 74 weeks + 4 days from now (10-Aug-2017).

All in all, the summary of this long post is

**Expected remaining time = [96,400,068/(total number of results calculated) - 1]*(elapsed time)**, bearing in mind that the number of calculated results/week is not the same every week.

Regards from Spain.

Ajedrecista.