Go Back > Factoring Projects > Operation Billion Digits

Thread Tools
Old 2022-11-13, 21:10   #34
clowns789's Avatar
Jun 2003
The Computer

401 Posts

Hi Ken, if necessary I can post my server specs again to get it qualification completed, or at least note that it is also an ECC system and all current P-1 assignments are using ECC RAM.
clowns789 is offline   Reply With Quote
Old 2022-11-13, 22:13   #35
kriesel's Avatar
Mar 2017
US midwest

2×3,767 Posts

Originally Posted by clowns789 View Post
Hi Ken, if necessary I can post my server specs again to get it qualification completed, or at least note that it is also an ECC system and all current P-1 assignments are using ECC RAM.
Qualifying as I laid it out involves being able to reproduce known factors, and to show run time scaling consistent with completion of good bounds OBD P-1 within 1-2 years solo. By now you have lots of iterations at OBD stage 1 to establish ~192M fft length iteration times. Some small ones (run to lookup gpu72 row bounds) from would be quick to run. Stage 2 would need ~64 GiB at OBD. ECC is one element of reliability but an errant CPU could make it miss a known factor.
kriesel is online now   Reply With Quote
Old 2023-03-02, 19:42   #36
kriesel's Avatar
Mar 2017
US midwest

2×3,767 Posts

Current TF & P-1 status is shown at Current indicated Level is 24.05.
3321928171 TF completed to 92 bits, 2022-02-05 by user johnny_jack, reserved for P-1, stage 2 5% complete
3321928307 TF completed to 92 bits, 2022-02-23 by kriesel; reserved for P-1, stage 2 ~14% complete on an ECC ram system
3321928319 TF completed to 92 bits, 2022-02-26 by kriesel; reserved for P-1, stage 2 ~16% complete on an ECC ram system
3321928373 TF completed to 92 bits, 2023-02-23 by kriesel; right to reserve P-1 by kriesel extends to 2023-03-23, and has NOT been ceded. (reserved anyway on the page by Rafael R for P-1 ~2023-03-02)

29 other exponents have been completed to 90 bits, and are available for reservation to a higher TF level.
These are in the exponent range up to 3321929987, as part of an effort to go to ~30 exponents eventually remaining with no known factors after TF and P-1 factoring completion to recommended levels and bounds, for eventual PRP/GEC/proof & CERT when hardware and software development advance sufficiently. Anyone with a sufficiently fast GPU, or fast CPU with at least 64 GiB ram, is welcome to help with TF or P-1 respectively. (But please follow the rules!)

At the moment:
OBD TF completed to 92 bits, reserved for P-1 and in progress in P-1 stage 2: 3
OBD TF completed to 92 bits, by Kriesel 2023-02-23, so restricted for reservation to kriesel until 2023-03-23: 1
OBD TF completed to 92 bits, ready for reservation by anyone with qualified hardware for P-1: 0
OBD TF completed to 91 bits: 0
OBD TF completed to 90 bits, reserved to 91 bits: 0

Systems with qualification(s) completed & posted for OBD P-1: 3 (1 is unconditionally)
Exponents completed thru stage 1 P-1: 3
Exponents completed thru stage 2 P-1: 0
kriesel is the only user that has yet posted system qualification results.

(This status summary is specific to OBD Mersennes. See also Ernst Mayer's F33 P-1 effort, mentioned in the Xeon Phi hardware thread.)
Attached Thumbnails
Click image for larger version

Name:	obd-2023-03-02.png
Views:	14
Size:	50.0 KB
ID:	28084  

Last fiddled with by kriesel on 2023-03-02 at 19:44
kriesel is online now   Reply With Quote
Old 2023-03-02, 22:58   #37
kriesel's Avatar
Mar 2017
US midwest

2·3,767 Posts
Default OBD P-1 coordination proposal revised

OBD P-1 is now feasible. For now, Mlucas v20.x is the only known software capable of OBD Mersenne P-1 factoring, with sufficiently large fft lengths and several months of QA testing and revision (patching) accomplished. The latest version is recommended, which is V20.1.1 patch 2022-07-06. See and

I propose the following:
  1. OBD candidates are taken to 92 bits TF done, before P-1 is attempted. (Due to run time, RTX206x or faster GPUs and mfaktx are recommended. TF reservations that would take longer than a year on available hardware ought be avoided.)
  2. P-1 is only attempted on OBD candidates with no known factors, except for software testing in which finding again a known factor supports confidence in the P-1 software on the tested FFT length.
  3. Whoever does the TF from 91 bits to 92 (which is half the total work of trial factoring an exponent up to 92 bits) gets first choice at reserving the P-1 for the same exponent, for the month following 92-bit completion. The individual may be operating under different usernames in the Mersenne forum and on Announcement in the OBD subforum of intent to complete a specific exponent's TF to 92 bits, followed by initiation and completion of that exponent to 92 bits under a different user name shall constitute sufficient proof that the two user names correspond to the same individual. That individual may retain priority on P-1 on the exponent by making a clear reservation on (or previously, in this thread), or cede the option to another specific individual or group, by posting clearly his intent in this thread including the recipient(s), or surrender the option entirely. (Something analogous to "I cede the option to reserve exponent 332192xxxx P-1 to user(s) insert-forum-name(s)-here".) Prior agreement by PM that the recipient(s) will commit to timely reserving and completing the P-1 is recommended in the case of ceding the option, as is prior qualification of hardware by the recipient(s). The option period does not reset upon ceding. Ceding recursively is discouraged. If the TF-to-92 user decides not to attempt P-1 on the exponent, announcing that in this thread promptly would be helpful.
  4. In the absence of a reservation by the TF-to-92-bits user (or if the option is ceded to others, by those others) and after a month past TF completion to 92 bits, or upon the TF-to-92 user posting its release before a month passes, the exponent becomes fair game for anyone with sufficient (qualified) hardware resources to reserve for P-1.
  5. P-1 is estimated to be ~21,663. GHzDays per attempt of both stages without factor found early, 5,220. GHzDays per attempt of stage 1 only, and require ~16 GiB of ECC ram in stage 1, ~64 GiB of ECC ram per system in stage 2. (128 GiB of ECC ram per system would be better in stage 2.) Those who haven't the hardware resources to complete that within a year ought not make solo P-1 reservations or attempts. (~59.4 GHzD/day minimum at ~192M fft length needed for completion of both stages solo within one year running continuously nonstop. Roughly a Xeon Phi 7210 or dual-12-core Xeon e5-2697v2)
  6. To qualify for reserving OBD exponents for P-1, post in this thread, results of run-time scaling derived from multiple widely-spaced exponents full P-1 runs, including near the first test wavefront, above 100Mdigit, and ideally also nearer 1Gbit, that demonstrates scaling consistent with completion within a year for OBD P-1, on the hardware planned to be used, along with a description of the software and hardware, sufficient for OBD P-1. Some run time scaling examples are posted at the Mlucas v20.1.x P-1 run time scaling reference post. Post title beginning with "Qualification" is suggested. To increase total possible throughput and participation, qualification either unconditionally, capable of completion of both stages within one year on one system, or conditionally, capable of completion within one year for a single stage or by splitting stage 2 with another equal or faster system, are allowed. Conditional qualifications should include " (conditional)" in the post title. Allow plenty of time for performing qualification, which may take weeks or months. Users intending to qualify multiple systems are encouraged to include a system name in each qualification post. Stating OS, Mlucas version, CPU model, available ram and type, and estimated OBD P-1 completion time are required.
  7. Optionally, systems tested and found to fail qualification may be posted, possibly saving others the time and effort of futile attempts to qualify similar hardware. At least the CPU model should be stated, and additional details required for qualification are encouraged. Post title should begin with "Disqualification".
  8. Reservation for OBD P-1 or TF is performed at Previously, P-1 reservation was, and for joint P-1 efforts still should include, posting a statement in this thread, of intent to P-1 factor a specific exponent. Post title "Reservation " followed by the exponent and whether the reservation is joint, solo, for both stages or only stage 1, is suggested. For example, "Reservation 3321928307 solo both P-1 stages", "Reservation 3321928171 joint both P-1 stages", "Reservation 3321928319 solo P-1 stage 1", "Reservation 3321928319 joint P-1 stage 2". Stage 2 is possible to do as a split effort with multiple systems, or joint effort with systems by multiple users; stage 1 is not. "Joint P-1 stage 1" is an oxymoron and constitutes an invalid reservation that will be ignored. Explicitly stating P-1 is proposed, to preclude possible uncertainty if P+1 or other multistage factoring becomes available for OBD exponents in the future.
  9. Joint reservations should be posted in this thread by the user who completed the TF to 92 bits (or by whomever he ceded the right to), if posting in the one-month option period. Otherwise reservation posting may be done by whoever is selected by mutual agreement in PM among the joint effort participants. All participants in a joint effort should be identified in the joint reservation post.
  10. P-1 reservations omitting joint, solo, or stage, from subject and body, will be presumed solo for both stages. Full specification is encouraged.
  11. P-1 reservations omitting identification of joint effort participants other than the poster may be treated as a single-user effort. Coordination and ensuring completion and result reporting in a joint effort is nominally the responsibility of the poster of the reservation.
  12. Use P-1 bounds corresponding to the target row for the exponent at shows B1=17,000,000, B2=1,000,000,000.
  13. Updating TF and P-1 assignment progress and ETA frequently at are strongly recommended. Reporting P-1 progress in this thread roughly monthly to quarterly is requested. (4-12 times per year.) Include exponent, stage, % complete, ETA. For joint efforts, update stage 2 progress by participant and system also. Dialogue by PM among joint participants for a specific reservation is recommended to establish participation, settle details such as stage 2 bounds split, etc (rather than chatty posting in this thread)
  14. Reservations expire after any of the following occur:
    1. One year passes after the last progress report that showed progress on that reservation.
    2. Two years pass after initial reservation.
    3. A factor is found and reported here.
    4. The user posts surrender of a reservation here.
    5. The factoring attempt is completed without finding a factor and is reported here. (In a joint attempt, that would require completion and reporting of all the reservation's participants' portions of the split stage 2.)
  15. If a new factor is found, or a reservation completed without finding a factor, it should be reported as a single line input in Or put the result(s) in a text file and upload at
  16. Reservation and other status for exponents 3321928171 through 3321929987 will be maintained in a Libre Office spreadsheet by kriesel, and periodic snapshots posted in this thread.
  17. Revision of reservations are to be avoided, but may be performed by posting clearly in this thread, for justifiable reasons such as time deadlines, equipment failure, etc, and must include the exponent and change. It might involve converting a solo reservation to joint, or shortening from both stages to stage 1. Revisions ought meet the same information content requirements as initial reservation.
  18. For reservations for only stage 1, the user should plan on preserving the stage 1 files until such time as a user reserves stage 2 on the same exponent, or a central repository for such files is established, and make all reasonable and necessary effort to transfer the stage 1 files for reuse, and ensure their correctness.
Constructive civil comments are invited.

Last fiddled with by kriesel on 2023-03-02 at 23:18
kriesel is online now   Reply With Quote
Old 2023-03-05, 17:54   #38
kriesel's Avatar
Mar 2017
US midwest

2×3,767 Posts

Originally Posted by kriesel View Post
(run to lookup gpu72 row bounds)
Since the pages have been changed, this is now called the target row.

Originally Posted by kriesel View Post
(reserved anyway on the page by Rafael R for P-1 ~2023-03-02)
Shortly after being made aware of this thread (IIUC by James Heinrich), Rafael R graciously unreserved M3321928373.
A proper P-1 on it requires ~21663. GHD, which would have been comparable effort to 3/4 of the total P-1 GHD credits for him in the preceding year. (Which I think were produced mostly by the more efficient new stage 2 code of mprime, while OBD P-1 requires Mlucas for sufficiently large fft length.) OBD work produces no GHD credits on, whether performing TF or P-1.

Exponent status update attached below.
Attached Files
File Type: pdf OBD exponent status 2023-03-05.pdf (24.6 KB, 11 views)

Last fiddled with by kriesel on 2023-03-05 at 18:00
kriesel is online now   Reply With Quote

Thread Tools

Similar Threads
Thread Thread Starter Forum Replies Last Post
A couple of 15e candidates fivemack NFS@Home 1 2014-11-30 07:52
How to calculate FFT lengths of candidates pepi37 Riesel Prime Search 8 2014-04-17 20:51
No available candidates on server japelprime Prime Sierpinski Project 2 2011-12-28 07:38
Adding New Candidates wblipp Operation Billion Digits 6 2011-04-10 17:45
new candidates for M...46 and M48 cochet Miscellaneous Math 4 2008-10-24 14:33

All times are UTC. The time now is 16:05.

Sun Mar 26 16:05:27 UTC 2023 up 220 days, 13:34, 1 user, load averages: 1.43, 1.03, 1.04

Powered by vBulletin® Version 3.8.11
Copyright ©2000 - 2023, Jelsoft Enterprises Ltd.

This forum has received and complied with 0 (zero) government requests for information.

Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 or any later version published by the Free Software Foundation.
A copy of the license is included in the FAQ.

≠ ± ∓ ÷ × · − √ ‰ ⊗ ⊕ ⊖ ⊘ ⊙ ≤ ≥ ≦ ≧ ≨ ≩ ≺ ≻ ≼ ≽ ⊏ ⊐ ⊑ ⊒ ² ³ °
∠ ∟ ° ≅ ~ ‖ ⟂ ⫛
≡ ≜ ≈ ∝ ∞ ≪ ≫ ⌊⌋ ⌈⌉ ∘ ∏ ∐ ∑ ∧ ∨ ∩ ∪ ⨀ ⊕ ⊗ 𝖕 𝖖 𝖗 ⊲ ⊳
∅ ∖ ∁ ↦ ↣ ∩ ∪ ⊆ ⊂ ⊄ ⊊ ⊇ ⊃ ⊅ ⊋ ⊖ ∈ ∉ ∋ ∌ ℕ ℤ ℚ ℝ ℂ ℵ ℶ ℷ ℸ 𝓟
¬ ∨ ∧ ⊕ → ← ⇒ ⇐ ⇔ ∀ ∃ ∄ ∴ ∵ ⊤ ⊥ ⊢ ⊨ ⫤ ⊣ … ⋯ ⋮ ⋰ ⋱
∫ ∬ ∭ ∮ ∯ ∰ ∇ ∆ δ ∂ ℱ ℒ ℓ
𝛢𝛼 𝛣𝛽 𝛤𝛾 𝛥𝛿 𝛦𝜀𝜖 𝛧𝜁 𝛨𝜂 𝛩𝜃𝜗 𝛪𝜄 𝛫𝜅 𝛬𝜆 𝛭𝜇 𝛮𝜈 𝛯𝜉 𝛰𝜊 𝛱𝜋 𝛲𝜌 𝛴𝜎𝜍 𝛵𝜏 𝛶𝜐 𝛷𝜙𝜑 𝛸𝜒 𝛹𝜓 𝛺𝜔