![]() |
1.3 GHz Thunderbird Athlon
|
Even though I am not yet an LMH (have to dig the 200MMX machine out and get it going),
I was wondering, is there any semi-co-ordinated work being done to thin out the predicted "sweet-spots"? Like the range near 33M? I would think that this is one where dealing out narrow bands to multiple people would lend to rapid completetion and then a run again at the next higher bit level. For example: The sweet spot peaks at say 33.35M, 3 workers on the team at first. Sliver up 33.0-33.7 into say 3 chunks to go from 2^60 - 2^61 Turn in results. Let one person work on the 2 side ranges upto 2^64 Split the center range in half and run up 2^62, then 2^63. Take the center range and split into 3 pieces, run to 2^64, adding a new body. Leave one working the two smaller ranges upto 2^66. Split the center again in half and run to 2^66 Split the range into 3 and add a memeber and run up to 2^67. Repeat until at least upto the predicted point of cost>benefit. Turn over sweetspot numbers to a crew with P-1 monsters. 400MB plus machines. |
Update from Sept 8:
- 849 new factors found, since the last update. - most activity on the 58 bit depth. [code:1] Bits Depth Diff ---- ------- ------ 57 26643 0 58 449775 (37413) 59 342963 19623 60 522670 14522 61 17220 1310 62 15911 966 63 4487 (257) 64 3710 251 65 3 0 66 8 0 67 6 0 68 6953 146 69 44 0 70 6 2 71 6 0 72 18 1 73 0 0 74 1 0 ---- ------- ------ Tot: 1390424 (849) [/code:1] |
[quote]Even though I am not yet an LMH (have to dig the 200MMX machine out and get it going),
For example: The sweet spot peaks at say 33.35M, 3 workers on the team at first. Sliver up 33.0-33.7 into say 3 chunks to go from 2^60 - 2^61 Turn in results. etc..... [/quote] 33.2-33.6 have been placed in PrimeNet, and are therefore not for usage by people in LMH. |
Update from the 21st of September:
57 26491 58 395727 59 350502 60 547489 61 28745 62 22317 63 5326 64 4265 65 3 66 8 67 6 68 7139 69 44 70 6 71 6 72 18 73 0 74 1 ---- ------- ------ Tot: 1388093 (2331) Keep going!... |
[code]
Bits Exponents (9/29/03) 57 26483 58 382203 59 342848 60 564292 61 29062 62 25100 63 5621 64 4346 65 3 66 8 67 6 68 7261 69 44 70 6 71 6 72 18 73 0 74 1 --------------- Total 1387308 (785) [/code] |
Some other vital statistics:
In the range of exponents from 25M to 79.3M, we expect to prove about 231991 exponents composite through trial factoring to GIMPS' proscribed factoring limits, and this will save about 4515695 P-90 CPU-years of first time LL tests. Below 25M, we expect to prove about 7982 exponents composite through trial factoring, and save about 18570 P-90 CPU-years of first time LL tests. Expected number of factors computed using factoring limits and probability function on [url]www.mersenne.org/math.htm[/url] (10/7/2003) and data from the 9/29/2003 edition of nofactor.cmp Cost computed with additional range and average cost data on [url]www.mersenne.org/status.htm[/url] (10/7/2003) Your milage may vary. |
[code]
Bits Exponents (10/8/2003) 57 19846 58 376607 59 320506 60 593270 61 28080 62 30499 63 5395 64 4572 65 3 66 8 67 6 68 7394 69 44 70 7 71 6 72 18 73 0 74 1 Total 1386262 (1046) [/code] Keep up the good work! |
[code]
Bits Exponents (10/23/03) 57 5624 58 369095 59 310528 60 615754 61 25987 62 39845 63 5396 64 4786 65 9 66 8 67 6 68 7661 69 44 70 7 71 6 72 18 73 0 74 1 Total 1384775 (1487) [/code] We seem to be moving a lot of exponents up from 57 bits, and 60 bits is rapidly becoming the next plateau. Good work all! |
Gosh! Somebody just did some 400000 range of exponents from 29.2 to 29.6M from 57 to 58. I have been carrying this range all the way up o 60 and doing 3 bits takes a lot of time but it sure feels bad to be poached!!
|
Sorry to hear that. Since the factoring reports don't keep user info, maybe we could get George to tell this other guy he's duplicating work?
|
| All times are UTC. The time now is 13:20. |
Powered by vBulletin® Version 3.8.11
Copyright ©2000 - 2023, Jelsoft Enterprises Ltd.