Run Database 55
Total Number of Runs: 1542 at depth=10
Date Started: Oct. 24, 2010
Completion: November 5-6, 2010 (estimated) All runs completed on November 3, 2010
S. No. | Branch | Allotted to | Date | Status | Run time | |
---|---|---|---|---|---|---|
1 | 1-25 | suresh_leo | Oct. 24 | Done | 12h 29m | |
2 | 26-50 | suresh_leo | Oct. 24 | Done | 18h 17m | |
3 | 51-75 | suresh_leo | Oct. 24 | Done | 23h 29m | |
4 | 76-100 | suresh_leo | Oct. 24 | Done | 24h 39m | |
5 | 101-125 | suresh_leo | Oct. 24 | Done | 12h 24m | |
6 | 126-150 | suresh_leo | Oct. 24 | Done | 23h 22m | |
7 | 151-175 | suresh_leo | Oct. 24 | Done | 23h 13m | |
8 | 176-225 | suresh_leo | Oct. 24 | Done | 56h 9m | |
9 | 226-275 | suresh_leo | Oct. 25 | Done | 78h 1m | |
10 | 276-325 | suresh_leo | Oct. 25 | Done | 33h | |
11 | 326-375 | suresh_leo | Oct. 25 | Done | 53h 55m | |
12 | 376-425 | suresh_leo | Oct. 25 | Done | 82h 12m | |
13 | 426-475 | suresh_leo | Oct. 25 | Done | 95h 23m | |
14 | 476-525 | suresh_leo | Oct. 25 | Done | 137h 34m | |
15 | 526-575 | suresh_leo | Oct. 25 | Done | 49h 44m | |
16 | 576-675 | suresh_leo | Oct. 25 | Done | 198h 13m | |
17 | 676-775 | suresh_leo | Oct. 26 | Done | 259h 21m | |
18 | 776-875 | suresh_leo | Oct. 26 | Done | 365h 50m | |
19 | 876-975 | suresh_leo | Oct. 26 | Done | 426h 37m | |
20 | 976-1050 | suresh_leo | Oct. 27 | Done | 165h 37m | |
21 | 1051-1125 | suresh_leo | Oct. 27 | Done | 253h 47m | |
22 | 1126-1200 | suresh_leo | Oct. 27 | Done | 253h 42m | |
23 | 1201-1275 | suresh_leo | Oct. 27 | Done | 394h* | |
24 | 1276-1350 | suresh_leo | Oct. 27 | Done | 260h 56m | |
25 | 1351-1450 | suresh_vega | Oct. 26 | Done | 557h* | |
26 | 1451-1542 | suresh_vega | Oct. 26 | Done | 863h* | ~ 4345h total |
* Estimated based on N=40 runs as the runs were on other machines.
Observations
- On an average it appears that each run needs about an hour of run time with the worst cases around 2-3 hours. In many ways, this appears to be a lot better than the N=52 run! Update: Now I see some runs of longer duration — about 4 hours. about 11 hours is the worst.
- It appears that the N=55 results will appear in around 7-8 days! Update: Looks difficult to meet the initial finish date of Nov. 5-6. Maybe off by a day or two.
- Based on test runs for some branches with N=60, I find that run times go up by around 12 times compared to the N=52 times. This will enable us to sort out the N=60 branches based on this estimate.
- Ran the code for N=40 to obtain run times. I find that one second for N=40 translates roughly to one hour for N=55.
- Due to the initial underestimate, several of the runs indicated above had to be split into further parts using estimates based on the N=40 runs. This is what one should have done in the first place.